mT5-XXL TPS calculator

Open weights Google,Google Research 13B parameters October 2020

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

509 cards that can run it

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 mT5-XXL?

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
Google,Google Research
Organisation type
Industry,Industry
Country
United States of America
Published
20 October 2020
Authors
Linting Xue, Noah Constant, Adam Roberts, Mihir Kale, Rami Al-Rfou, Aditya Siddhant, Aditya Barua, Colin Raffel

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Language
Task
Language modeling, Translation, Language modeling/generation, Question answering

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

13 billion

Training data
1,000,000,000,000 tokens

The model was trained on a subset of 1 trillion tokens. Full mC4 corpus has data "totaling 6.6B pages and 6.3T tokens" Distribution by language is in Appendix A.

Batch size
1,048,576

"We pre-train our mT5 model variants for 1 million steps on batches of 1024 length-1024 input sequences, corresponding to roughly 1 trillion input tokens total."

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
8.2 × 10²² FLOP

"We pre-train our mT5 model variants for 1 million steps on batches of 1024 length-1024 input sequences, corresponding to roughly 1 trillion input tokens total." 1 million steps * 1024 batchsize * 1024 length * 13 billion params * 6 = 8.2e22 Ignores fine-tuning compute; this is likely a small fraction of pre-training compute.

How it was established
Operation counting

The training run

What it physically took to train: which chips, how many, for how long, and what that drew from the wall.

Compute cost
$179,442

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
Open source

Apache 2.0 license training code: https://github.com/google-research/multilingual-t5

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Frontier model
Yes
Why it is tracked
Highly cited,SOTA improvement

"Table 2 presents our main results, with perlanguage breakdowns for each task given in Appendix B. Our largest model mT5-XXL exceeds state-of-the-art on all classification and QA tasks and is near SOTA on NER (69.2 vs. 70.1)."

Record confidence
Confident
Citations
2,892

Sources

Where this record came from and when it was last checked.

Reference
mT5: A Massively Multilingual Pre-trained Text-to-Text Transformer
Last updated
6 January 2026

The extremes

What the numbers mean

What it takes to run this model

Minimum card

Xeon Phi 5110P

Memory needed

7.1 GB

Fastest

261 tok/s

mT5-XXL 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.

The smallest card that holds it is the Xeon Phi 5110P with 8 GB, running it at Q3_K_M and producing around 18.3 tokens per second.

A B200 is the fastest we calculate for it: about 261 tokens per second, from 8,000 GB/s of memory bandwidth.

Background

mT5-XXL was published by Google,Google Research, in United States of America, in October 2020. The organisation is categorised as industry,Industry.

It works in Language, and is recorded as doing language modeling, Translation, Language modeling/generation, Question answering.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.

Reading the throughput figures

Across every card that can run it, the middle of the range is about 21.2 tokens per second, and 459 of them clear the ten tokens per second that roughly matches reading speed.

Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.

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

Training it took roughly 8.2 × 10²² FLOP of computation — a measure of what producing the model cost, not of how fast it answers.

Around 1,000,000,000,000 tokens went into training it.

It is tracked in the underlying dataset for one reason in particular: highly cited,SOTA improvement.

Step by step

How to choose a GPU for mT5-XXL

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Read the memory figure first

    The table lists every card that can hold mT5-XXL — around 7.1 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.

  2. 02

    Match the context to your actual use

    Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for mT5-XXL.

  3. 03

    Decide how much compression you will accept

    The quantisation column varies by card, because a bigger card holds a more accurate copy of mT5-XXL — Q3_K_M on the smallest card that fits. Set a floor to hold the comparison at one level.

  4. 04

    Rank by throughput rather than spec sheet

    Ranking by tokens per second for mT5-XXL follows memory bandwidth, not core counts, which is why the B200 tops it at 261 tok/s.

  5. 05

    Read the fit column last

    A tight fit runs mT5-XXL but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.

  6. 06

    See what else that card runs

    Following a card through to its own page shows every other model it can hold, which is the question that follows once mT5-XXL is settled.

Answers

mT5-XXL — common questions

01

Can I run mT5-XXL 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.

02

Can I run mT5-XXL 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.

03

Can I run mT5-XXL 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.

04

Can I run mT5-XXL 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.

05

Is mT5-XXL open source?

Its weights are published, so mT5-XXL 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.

06

How many parameters does mT5-XXL have?

mT5-XXL has 13B parameters. 13 billion. 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.

07

Who created mT5-XXL?

mT5-XXL was published by Google,Google Research, based in United States of America, categorised as industry,Industry.

08

When was mT5-XXL released?

mT5-XXL was published in October 2020. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

09

What is mT5-XXL used for?

mT5-XXL works in Language, and is recorded as handling language modeling, Translation, Language modeling/generation, Question answering. These are the areas it was designed around; they describe intent rather than a hard boundary.

10

Where can I download mT5-XXL?

The weights for mT5-XXL are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

11

How much compute was used to train mT5-XXL?

Around 8.2 × 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.

12

Can I run mT5-XXL if it does not fit in my GPU?

It can be split between the card and system memory, but mT5-XXL generates painfully slowly that way — the nearest miss we calculate is short by 3.2 GB. Nothing on this page assumes offloading.

13

Would two GPUs run mT5-XXL faster?

Two cards buy memory rather than speed. That matters for mT5-XXL only if one card cannot hold it — 509 can, so a second adds little.

14

Why does the quantisation differ between cards for mT5-XXL?

Each card is shown running the least-compressed copy it can hold, and mT5-XXL appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.

15

How accurate are these mT5-XXL speed estimates?

These are estimates with real error bars. The fastest result here, 156–417 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.

16

What GPU do I need to run mT5-XXL?

The smallest card in our catalogue that holds mT5-XXL 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.

17

How fast is mT5-XXL 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 mT5-XXL clear that.

18

How much VRAM does mT5-XXL 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.

Source

Original publication

Record last updated 6 January 2026

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.