mT0-13B 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
Xeon Phi 5110P
8 GB · Q3_K_M · 18.3 tok/s
Fastest card
B200
261 tok/s · 180 GB
Which GPUs can run mT0-13B?
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.
509 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
261
tok/s
156–417 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 14.6 GB | Q8_0 | Comfortable |
|
261
tok/s
156–417 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 14.6 GB | Q8_0 | Comfortable |
|
208
tok/s
125–333 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 14.6 GB | Q8_0 | Comfortable |
|
208
tok/s
125–333 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 14.6 GB | Q8_0 | Comfortable |
|
166
tok/s
100–266 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 14.6 GB | Q8_0 | Comfortable |
|
159
tok/s
96–255 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 14.6 GB | Q8_0 | Comfortable |
|
159
tok/s
96–255 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 14.6 GB | Q8_0 | Comfortable |
|
152
tok/s
91–244 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 14.6 GB | Q8_0 | Comfortable |
|
135
tok/s
81–217 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 14.6 GB | Q8_0 | Comfortable |
|
135
tok/s
81–217 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 14.6 GB | Q8_0 | Comfortable |
|
135
tok/s
81–217 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 14.6 GB | Q8_0 | Comfortable |
|
131
tok/s
79–210 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 7.1 GB | Q3_K_M | Tight |
|
128
tok/s
77–205 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 14.6 GB | Q8_0 | Comfortable |
|
117
tok/s
70–188 · low confidence |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.6 GB | Q4_K_M | Tight |
|
109
tok/s
66–175 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 14.6 GB | Q8_0 | Comfortable |
|
109
tok/s
66–175 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 14.6 GB | Q8_0 | Comfortable |
|
109
tok/s
66–175 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 14.6 GB | Q8_0 | Comfortable |
|
109
tok/s
66–175 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 14.6 GB | Q8_0 | Comfortable |
|
109
tok/s
66–175 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 14.6 GB | Q8_0 | Comfortable |
|
83.4
tok/s
50–133 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 14.6 GB | Q8_0 | Comfortable |
|
83.4
tok/s
50–133 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 14.6 GB | Q8_0 | Comfortable |
|
69.5
tok/s
42–111 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 14.6 GB | Q8_0 | Comfortable |
|
68.0
tok/s
41–109 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 14.6 GB | Q8_0 | Comfortable |
|
67.5
tok/s
41–108 · low confidence |
RTX A5000-8Q NVIDIA | 8 GB | 768 GB/s | Apr 2021 | 7.1 GB | Q3_K_M | Tight |
|
66.5
tok/s
40–106 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 14.6 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.
- Organisation
- Hugging Face,BigScience
- Organisation type
- Industry,Research collective
- Country
- United States of America, France
- Published
- 3 November 2022
- Authors
- Niklas Muennighoff, Thomas Wang, Lintang Sutawika, Adam Roberts, Stella Biderman, Teven Le Scao, M Saiful Bari, Sheng Shen, Zheng-Xin Yong, Hailey Schoelkopf, Xiangru Tang, Dragomir Radev, Alham Fikri Aji, Khalid Almubarak, Samuel Albanie, Zaid Alyafeai, Albert Webson, Edward Raff, Colin Raffel
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Translation, Language modeling/generation
- Base model
- mT5-XXL
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
- 13B
- Training data
- 20,000,000,000 tokens
13B
per https://huggingface.co/datasets/bigscience/xP3, 94,941,936 KB or 94GB if approx 200M words per GB, that's ~20B words (rougher estimate because it's multilingual) https://docs.google.com/document/d/1G3vvQkn4x_W71MKg0GmHVtzfd9m0y3_Ofcoew0v902Q/edit#heading=h.ieihc08p8dn0
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.
- Fine-tuning compute
- 1 × 10²¹ FLOP
"We finetune the models for an additional 13 billion tokens with loss only being computed on target tokens... For finetuning mT5, we follow the same procedure as described above for BLOOM, except that inputs are fed into the encoder and thus are not space-separated from targets." 13B * 13B * 6 = 1.01e21
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)
- Training code
- Unreleased
apache 2.0
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Why it is tracked
- SOTA improvement
- Record confidence
- Confident
- Citations
- 242
"Finetuning on multilingual tasks with English prompts further improves performance on English and non-English tasks leading to various state-of-the-art zero-shot results." Figure 4, zero-shot SOTA
Sources
Where this record came from and when it was last checked.
- Reference
- Crosslingual Generalization through Multitask Finetuning
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run mT0-13B
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 261 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 261 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 208 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 208 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 166 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 159 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 159 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 152 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 135 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 135 tok/s
The smallest GPUs that still run mT0-13B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Radeon RX 7400 8 GB · needs 7.1 GB · Q3_K_M · tight 19.8 tok/s
- 02 Radeon RX 9060 8 GB · needs 7.1 GB · Q3_K_M · tight 22.1 tok/s
- 03 GeForce RTX 5050 8 GB · needs 7.1 GB · Q3_K_M · tight 28.1 tok/s
- 04 GeForce RTX 5050 Mobile 8 GB · needs 7.1 GB · Q3_K_M · tight 33.8 tok/s
- 05 Radeon RX 9060 XT 8 GB 8 GB · needs 7.1 GB · Q3_K_M · tight 22.1 tok/s
- 06 GeForce RTX 5060 Mobile 8 GB · needs 7.1 GB · Q3_K_M · tight 33.8 tok/s
- 07 GeForce RTX 5060 8 GB · needs 7.1 GB · Q3_K_M · tight 39.4 tok/s
- 08 GeForce RTX 5060 Ti 8 GB 8 GB · needs 7.1 GB · Q3_K_M · tight 39.4 tok/s
- 09 GeForce RTX 5070 Mobile 8 GB · needs 7.1 GB · Q3_K_M · tight 33.8 tok/s
- 10 Radeon RX 7650 GRE 8 GB · needs 7.1 GB · Q3_K_M · tight 19.8 tok/s
What the numbers mean
The hardware side
Minimum card
Xeon Phi 5110P
Memory needed
7.1 GB
Fastest
261 tok/s
mT0-13B is small enough at 13B parameters that hardware is rarely the obstacle — 509 of the cards we track can run it, including cards several years old.
At the low end, a Xeon Phi 5110P handles it — 8 GB, at Q3_K_M, for about 18.3 tokens per second.
At the other end, a B200 generates roughly 261 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
Background
mT0-13B was published by Hugging Face,BigScience, in United States of America, in November 2022. industry,Research collective is the category the publisher falls under.
It works in Language, and is recorded as doing translation, Language modeling/generation.
Its starting point was mT5-XXL — most models at this scale are adapted from an existing base rather than built from nothing.
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
The median result is around 21.2 tokens per second; 459 cards produce text faster than most people read it.
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
Around 20,000,000,000 tokens went into training it.
The reason it appears in this catalogue at all is sOTA improvement.
Step by step
How to choose a GPU for mT0-13B
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 mT0-13B — around 7.1 GB at Q3_K_M. Capacity is the gate — a card either holds it or it does not.
-
02
Set the context length you will work at
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason mT0-13B stops fitting a card that seemed fine.
-
03
Set a quality floor
The quantisation column varies by card, because a bigger card holds a more accurate copy of mT0-13B — Q3_K_M on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Compare tokens per second, not specifications
The speed ordering for mT0-13B is effectively an ordering by memory bandwidth, which is why the B200 tops it at 261 tok/s.
-
05
Look at the headroom, not just the fit
A tight fit runs mT0-13B but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
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 mT0-13B is settled.
Answers
mT0-13B — common questions
Is mT0-13B open source?
Its weights are published, so mT0-13B 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 mT0-13B have?
mT0-13B has 13B parameters. 13B. 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.
Who created mT0-13B?
mT0-13B was published by Hugging Face,BigScience, based in United States of America, categorised as industry,Research collective.
When was mT0-13B released?
mT0-13B was published in November 2022. 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 mT0-13B used for?
mT0-13B works in Language, and is recorded as handling translation, Language modeling/generation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download mT0-13B?
The weights for mT0-13B are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Can I run mT0-13B if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down — the nearest miss we calculate is short by 3.2 GB. Our figures for mT0-13B assume it is fully resident.
Would two GPUs run mT0-13B faster?
Capacity adds across cards; throughput does not. Since 509 of the cards we track already hold mT0-13B on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for mT0-13B?
Each card is shown running the least-compressed copy it can hold, and mT0-13B appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these mT0-13B speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 156–417 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
What GPU do I need to run mT0-13B?
The smallest card in our catalogue that holds mT0-13B is the Xeon Phi 5110P, with 8 GB of memory. It runs the model at Q3_K_M using about 7.1 GB, and produces roughly 18.3 tokens per second. 509 cards in total can run it.
How fast is mT0-13B on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 261 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 459 of the cards that can run mT0-13B clear that.
How much VRAM does mT0-13B need?
About 7.1 GB at Q3_K_M 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 mT0-13B on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q3_K_M, using about 7.1 GB and generating roughly 131 tokens per second — a tight fit.
Can I run mT0-13B on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q5_K_M, using about 10.1 GB and generating roughly 53.1 tokens per second — a tight fit.
Can I run mT0-13B on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q6_K, using about 11.6 GB and generating roughly 53.5 tokens per second — a comfortable fit.
Can I run mT0-13B on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 14.6 GB and generating roughly 43.7 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.