OuteTTS-0.1-350M TPS calculator
Each card below is assessed against this model at the context length and minimum quality you choose. Speed is an estimate for a single request, calculated from the card's memory bandwidth and the size of the model once compressed.
Calculated for this model
818 cards we hold specifications for
Smallest card that fits
Tesla C1080
4 GB · Q8_0 · 105 tok/s
Fastest card
B200
9,681 tok/s · 180 GB
Which GPUs can run OuteTTS-0.1-350M?
Set the inputs, read the answer
A longer conversation needs more memory, which can push this model off smaller cards.
Hides cards that would only fit the model by compressing it below this point.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
9,681
tok/s
5,808–15,489 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.1 GB | Q8_0 | Comfortable |
|
9,681
tok/s
5,808–15,489 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.1 GB | Q8_0 | Comfortable |
|
7,730
tok/s
4,638–12,368 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
7,730
tok/s
4,638–12,368 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
6,182
tok/s
3,709–9,892 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,917
tok/s
3,550–9,468 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,917
tok/s
3,550–9,468 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,663
tok/s
3,398–9,061 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,026
tok/s
3,016–8,042 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,026
tok/s
3,016–8,042 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,026
tok/s
3,016–8,042 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,768
tok/s
2,861–7,628 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,066
tok/s
2,440–6,505 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,066
tok/s
2,440–6,505 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.1 GB | Q8_0 | Comfortable |
|
4,066
tok/s
2,440–6,505 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,066
tok/s
2,440–6,505 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,066
tok/s
2,440–6,505 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,096
tok/s
1,858–4,953 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
3,096
tok/s
1,858–4,953 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,580
tok/s
1,548–4,128 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,525
tok/s
1,515–4,040 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,469
tok/s
1,481–3,950 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.1 GB | Q8_0 | Comfortable |
|
2,469
tok/s
1,481–3,950 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,469
tok/s
1,481–3,950 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.1 GB | Q8_0 | Comfortable |
|
2,469
tok/s
1,481–3,950 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
Speeds are estimates for a single request — one conversation at a time — calculated from memory bandwidth, model size and quantisation. Real throughput varies with the inference runtime and its version. Figures published by hardware vendors measure many simultaneous requests and are much higher.
On record
Full specification
Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.
Origin
Who built this model, where, and when it was published.
- Published
- 12 August 2024
- Authors
- OuteAI
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Speech
- Task
- Text-to-speech (TTS)
Size
How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.
- Parameters
- 350M
- Training data
- tokens
The Safetensors card in [1] lists the model size as 362M parameters, but the Limitations and Model details sections in [1], as well as the Abstract and Introduction sections in [2], specifically say the model size is 350M parameters. Since there are more sources saying the model has 350M parameters, I went with this figure. 1. https://huggingface.co/OuteAI/OuteTTS-0.1-350M 2. https://outeai.com/blog/outetts-0.1-350m
DCLM-baseline-1.0 is a text dataset [1], and since OuteTTS-0.1-350M generates speech, I will assume that the dataset can be measured in words. The model currently supports only English [2], so I will assume that it was trained on English text only. Assuming 0.75 English words per token [3], Dataset size = 30e9 tokens * 0.75 words / token = 22.5e9 words = 2.25e10 words 1. https://arxiv.org/pdf/2406.11794 2. https://huggingface.co/OuteAI/OuteTTS-0.1-350M 3. https://docs.google.com/document/d/1XWLy…
Training compute
The arithmetic performed to train the model, measured in floating-point operations. It is a measure of what the training run cost, not of how fast the finished model answers you.
- Training compute
- 6.3 × 10¹⁹ FLOP
Training compute = # of active parameters / forward pass * # of tokens * 6 FLOPS / token = 350e6 parameters * 30e9 tokens * 6 FLOPS / token = 63000e15 FLOPS = 6.3e19 FLOPS, using the 6ND approximation and assuming the model architecture is dense.
Availability
Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.
- Weights
- Open — downloadable
- Model access
- Open weights (unrestricted)
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- OuteTTS-0.1-350M
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run OuteTTS-0.1-350M
Ranked by estimated tokens per second, newest card first where speeds tie. Because generation is bound by memory bandwidth, this ordering follows bandwidth rather than any gaming benchmark.
- 01 B300 288 GB · 8,000 GB/s · Q8_0 9,681 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 9,681 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 7,730 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 7,730 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 6,182 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 5,917 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 5,917 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 5,663 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 5,026 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 5,026 tok/s
The smallest GPUs that still run OuteTTS-0.1-350M
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 1.1 GB · Q8_0 · comfortable 116 tok/s
- 02 RTX A400 4 GB · needs 1.1 GB · Q8_0 · comfortable 116 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.1 GB · Q8_0 · comfortable 155 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.1 GB · Q8_0 · comfortable 232 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.1 GB · Q8_0 · comfortable 41.3 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.1 GB · Q8_0 · comfortable 121 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.1 GB · Q8_0 · comfortable 136 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.1 GB · Q8_0 · comfortable 121 tok/s
- 09 Arc A310 4 GB · needs 1.1 GB · Q8_0 · comfortable 97.5 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.1 GB · Q8_0 · comfortable 101 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Tesla C1080
Memory needed
1.1 GB
Fastest
9,681 tok/s
OuteTTS-0.1-350M is small enough at 350M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The smallest card that holds it is the Tesla C1080 with 4 GB, running it at Q8_0 and producing around 105 tokens per second.
The quickest result comes from a B200 at around 9,681 tokens per second — its 8,000 GB/s of bandwidth is what buys that.
Background
OuteTTS-0.1-350M was published by its authors, in August 2024.
It works in Speech, and is recorded as doing text-to-speech (TTS).
Published weights mean the model runs on your machine rather than someone else's, which is what makes the hardware question below answerable at all.
Reading the throughput figures
Across every card that can run it, the middle of the range is about 271.8 tokens per second, and 817 of them clear the ten tokens per second that roughly matches reading speed.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
How it was trained
The training run consumed about 6.3 × 10¹⁹ FLOP. That figure describes the cost of creating it and has no bearing on how quickly it generates text.
Step by step
How to choose a GPU for OuteTTS-0.1-350M
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Start from the memory column
Every card here has been checked against OuteTTS-0.1-350M — around 1.1 GB at Q8_0. Capacity is the gate — a card either holds it or it does not.
-
02
Match the context to your actual use
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason OuteTTS-0.1-350M stops fitting a card that seemed fine.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage OuteTTS-0.1-350M by squeezing it further than you would want.
-
04
Sort by speed
The speed ordering for OuteTTS-0.1-350M is effectively an ordering by memory bandwidth, which is why the B200 tops it at 9,681 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage OuteTTS-0.1-350M from those with room to spare. Buy for the second if the context might grow.
-
06
Open the card you have settled on
Following a card through to its own page shows every other model it can hold, which is the question that follows once OuteTTS-0.1-350M is settled.
Answers
OuteTTS-0.1-350M — common questions
Is OuteTTS-0.1-350M open source?
Its weights are published, so OuteTTS-0.1-350M can be downloaded and run on your own hardware. Note that open weights is not the same as open source in the full sense — it says nothing about the training data, the training code, or the commercial terms attached.
How many parameters does OuteTTS-0.1-350M have?
OuteTTS-0.1-350M has 350M parameters. The Safetensors card in [1] lists the model size as 362M parameters, but the Limitations and Model details sections in [1], as well as the Abstract and Introduction sections in [2], specifically say the model size is 350M parameters. Since there are more sources saying the model has 350M parameters, I went with this figure. 1. https://huggingface.co/OuteAI/OuteTTS-0.1-350M 2. https://outeai.com/blog/outetts-0.1-350m. That figure is the total, and it is what decides how much memory the model needs — roughly half a gigabyte per billion at the compression most people use.
When was OuteTTS-0.1-350M released?
OuteTTS-0.1-350M was published in August 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
What is OuteTTS-0.1-350M used for?
OuteTTS-0.1-350M works in Speech, and is recorded as handling text-to-speech (TTS). These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download OuteTTS-0.1-350M?
The weights for OuteTTS-0.1-350M are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train OuteTTS-0.1-350M?
Around 6.3 × 10¹⁹ FLOP. That measures what producing the model cost and says nothing about how quickly it answers once trained — inference speed comes from memory bandwidth, not from the training budget.
Can I run OuteTTS-0.1-350M if it does not fit in my GPU?
It can be split between the card and system memory, but OuteTTS-0.1-350M generates painfully slowly that way. Nothing on this page assumes offloading.
Would two GPUs run OuteTTS-0.1-350M faster?
Two cards buy memory rather than speed. That matters for OuteTTS-0.1-350M only if one card cannot hold it — 818 can, so a second adds little.
Why does the quantisation differ between cards for OuteTTS-0.1-350M?
Each card is shown running the least-compressed copy it can hold, and OuteTTS-0.1-350M appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these OuteTTS-0.1-350M speed estimates?
Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 5,808–15,489 tok/s on the B200 rather than a single number.
What GPU do I need to run OuteTTS-0.1-350M?
The smallest card in our catalogue that holds OuteTTS-0.1-350M is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.1 GB, and produces roughly 105 tokens per second. 818 cards in total can run it.
How fast is OuteTTS-0.1-350M on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 9,681 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 817 of the cards that can run OuteTTS-0.1-350M clear that.
How much VRAM does OuteTTS-0.1-350M need?
About 1.1 GB at Q8_0 compression, which is what the smallest card that runs it uses. Less compression needs more: the figures in the memory column above are recalculated for each card, because each one holds the least-compressed version it can.
Can I run OuteTTS-0.1-350M on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,803 tokens per second — a comfortable fit.
Can I run OuteTTS-0.1-350M on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,104 tokens per second — a comfortable fit.
Can I run OuteTTS-0.1-350M on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,367 tokens per second — a comfortable fit.
Can I run OuteTTS-0.1-350M on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.1 GB and generating roughly 1,622 tokens per second — a comfortable fit.
The other direction
Looking at it from the other side?
This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.