UL2 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
Quadro K6000
12 GB · Q3_K_M · 14.0 tok/s
Fastest card
B200
169 tok/s · 180 GB
Which GPUs can run UL2?
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.
293 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
169
tok/s
102–271 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 22.1 GB | Q8_0 | Comfortable |
|
169
tok/s
102–271 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 22.1 GB | Q8_0 | Comfortable |
|
135
tok/s
81–216 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 22.1 GB | Q8_0 | Comfortable |
|
135
tok/s
81–216 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 22.1 GB | Q8_0 | Comfortable |
|
108
tok/s
65–173 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 22.1 GB | Q8_0 | Comfortable |
|
104
tok/s
62–166 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 22.1 GB | Q8_0 | Comfortable |
|
104
tok/s
62–166 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 22.1 GB | Q8_0 | Comfortable |
|
99.1
tok/s
59–159 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 22.1 GB | Q8_0 | Comfortable |
|
88.0
tok/s
53–141 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 22.1 GB | Q8_0 | Comfortable |
|
88.0
tok/s
53–141 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 22.1 GB | Q8_0 | Comfortable |
|
88.0
tok/s
53–141 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 22.1 GB | Q8_0 | Comfortable |
|
83.4
tok/s
50–134 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 22.1 GB | Q8_0 | Comfortable |
|
71.2
tok/s
43–114 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 22.1 GB | Q8_0 | Comfortable |
|
71.2
tok/s
43–114 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 22.1 GB | Q8_0 | Comfortable |
|
71.2
tok/s
43–114 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 22.1 GB | Q8_0 | Comfortable |
|
71.2
tok/s
43–114 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 22.1 GB | Q8_0 | Comfortable |
|
71.2
tok/s
43–114 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 22.1 GB | Q8_0 | Comfortable |
|
55.2
tok/s
33–88 · low confidence |
Tesla V100 SXM2 16 GB NVIDIA | 16 GB | 1,130 GB/s | Nov 2019 | 12.8 GB | Q4_K_M | Tight |
|
54.2
tok/s
33–87 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 22.1 GB | Q8_0 | Comfortable |
|
54.2
tok/s
33–87 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 22.1 GB | Q8_0 | Comfortable |
|
52.1
tok/s
31–83 · low confidence |
GeForce RTX 3080 12 GB NVIDIA | 12 GB | 912 GB/s | Jan 2022 | 10.5 GB | Q3_K_M | Tight |
|
52.1
tok/s
31–83 · low confidence |
GeForce RTX 3080 Ti NVIDIA | 12 GB | 912 GB/s | May 2021 | 10.5 GB | Q3_K_M | Tight |
|
46.9
tok/s
28–75 · low confidence |
GeForce RTX 5080 NVIDIA | 16 GB | 960 GB/s | Jan 2025 | 12.8 GB | Q4_K_M | Tight |
|
45.2
tok/s
27–72 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 22.1 GB | Q8_0 | Comfortable |
|
44.2
tok/s
27–71 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 22.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.
- Organisation
- Google Research,Google Brain
- Organisation type
- Industry,Industry
- Country
- United States of America
- Published
- 10 May 2022
- Authors
- Yi Tay, Mostafa Dehghani, Vinh Q. Tran, Xavier Garcia, Dara Bahri, Tal Schuster, Huaixiu Steven Zheng, Neil Houlsby, Donald Metzler
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Question answering, Text summarization
- Numerical format
- BF16
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
- 20B
- Training data
- 1,000,000,000,000 tokens
- Batch size
- 524,288
Taken from Directory of LLMs
1T tokens
1024 * 512
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
- 1.2 × 10²³ FLOP
- How it was established
- Hardware,Operation counting
Trained on 1T tokens 20B * 1T * 6 = 1.2e23 Second source: Section 5.1 says model was trained on 512 TPUv4 chips, and took slightly over 1 month 512 * 2.75e14 * 31 * 24 * 3600 * 0.3 = 1.13e23
The training run
What it physically took to train: which chips, how many, for how long, and what that drew from the wall.
- Training hardware
- Google TPU v4
- Chips used
- 512
- Chip-hours
- 380,928
- Wall-clock time
- 744 hours (31 days)
- Hardware utilisation
- MFU 29.9%
- Power draw
- 349.6 kW
- Compute cost
- $126,786
around 31 days from 'Pre-training took approximately slight more than one month for about 1 trillion tokens.' from section 5.1 so around 31*24 = 744
"Pretraining took slightly longer than 1 month" to train on 1T tokens using 512 TPUv4 chips. ops-counting method gives 1.20e23 FLOP needed to train, and 512 TPUv4s running at max FLOPs for 1.1 months is: 1.1 * 30 * 24 * 3600 * 512 * 2.75e14 = 4.01e23 FLOP 1.2e23 / 4.01e23 = MFU = 0.29925
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
- Hugging Face
Apache 2.0 https://huggingface.co/google/ul2
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Foundation model
- Yes
- Likely above 10²³ FLOP
- Yes
- Why it is tracked
- SOTA improvement
- Record confidence
- Confident
- Citations
- 387
"by scaling our model up to 20B parameters, we achieve SOTA performance on 50 well-established supervised NLP tasks"
Sources
Where this record came from and when it was last checked.
- Reference
- Unifying Language Learning Paradigms
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run UL2
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 169 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 169 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 135 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 135 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 108 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 104 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 104 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 99.1 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 88.0 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 88.0 tok/s
The smallest GPUs that still run UL2
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Switch 2 GPU 12 GB · needs 10.5 GB · Q3_K_M · tight 5.9 tok/s
- 02 Radeon RX 9070 GRE 12 GB · needs 10.5 GB · Q3_K_M · tight 19.3 tok/s
- 03 GeForce RTX 5070 12 GB · needs 10.5 GB · Q3_K_M · tight 38.4 tok/s
- 04 GeForce RTX 5070 Ti Mobile 12 GB · needs 10.5 GB · Q3_K_M · tight 38.4 tok/s
- 05 Arc B580 12 GB · needs 10.5 GB · Q3_K_M · tight 16.9 tok/s
- 06 Radeon RX 7800M 12 GB · needs 10.5 GB · Q3_K_M · tight 19.3 tok/s
- 07 GeForce RTX 4070 GDDR6 12 GB · needs 10.5 GB · Q3_K_M · tight 27.4 tok/s
- 08 GeForce RTX 4070 AD103 12 GB · needs 10.5 GB · Q3_K_M · tight 28.8 tok/s
- 09 GeForce RTX 4070 SUPER 12 GB · needs 10.5 GB · Q3_K_M · tight 28.8 tok/s
- 10 Radeon RX 6750 GRE 12 GB 12 GB · needs 10.5 GB · Q3_K_M · tight 19.3 tok/s
What the numbers mean
What you need to run it
Minimum card
Quadro K6000
Memory needed
10.5 GB
Fastest
169 tok/s
With 20B parameters, UL2 lands in the range a serious desktop card can handle once the weights are compressed. 293 of the cards we track can run it.
The least hardware that works is a Quadro K6000. Its 12 GB is enough at Q3_K_M compression, giving roughly 14.0 tokens per second.
Top of the range is the B200, at roughly 169 tokens per second thanks to 8,000 GB/s of bandwidth.
What this model is
UL2 was published by Google Research,Google Brain, in United States of America, in May 2022. It comes out of industry,Industry.
It works in Language, and is recorded as doing language modeling/generation, Question answering, Text summarization.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. It is published under the google organisation on Hugging Face.
What decides the speed
Half the cards that hold it manage more than 20.6 tokens per second, and 248 exceed reading speed outright.
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.
Its internal architecture is not on file, so memory is approximated from the parameter count and marked accordingly. Expect the real figure to differ, more so at long context.
Training and provenance
Training it took roughly 1.2 × 10²³ FLOP of computation, on Google TPU v4 — 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: sOTA improvement.
Step by step
How to choose a GPU for UL2
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Read the memory figure first
Every card here has been checked against UL2 — around 10.5 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 UL2 stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
The quantisation column varies by card, because a bigger card holds a more accurate copy of UL2 — Q3_K_M on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Rank by throughput rather than spec sheet
The speed ordering for UL2 is effectively an ordering by memory bandwidth, which is why the B200 tops it at 169 tok/s.
-
05
Look at the headroom, not just the fit
A tight fit runs UL2 but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
06
Check the card from the other side
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond UL2.
Answers
UL2 — common questions
Can I run UL2 on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q3_K_M, using about 10.5 GB and generating roughly 52.1 tokens per second — a tight fit.
Can I run UL2 on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q4_K_M, using about 12.8 GB and generating roughly 55.2 tokens per second — a tight fit.
Can I run UL2 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q6_K, using about 17.5 GB and generating roughly 41.2 tokens per second — a comfortable fit.
Is UL2 open source?
Its weights are published, so UL2 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 UL2 have?
UL2 has 20B parameters. Taken from Directory of LLMs. 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 UL2?
UL2 was published by Google Research,Google Brain, based in United States of America, categorised as industry,Industry.
When was UL2 released?
UL2 was published in May 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 UL2 used for?
UL2 works in Language, and is recorded as handling language modeling/generation, Question answering, Text summarization. These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download UL2?
Its weights are published under the google organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train UL2?
Around 1.2 × 10²³ FLOP, on Google TPU v4. 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 UL2 if it does not fit in my GPU?
Partly. Layers that do not fit sit in system memory and run at a fraction of the speed, so a mostly-offloaded UL2 is rarely worth using — the nearest miss we calculate is short by 2.9 GB. Every figure here assumes the whole model is on the card.
Would two GPUs run UL2 faster?
A second card roughly doubles the memory available but not the generation rate. With 293 cards already able to run UL2 alone, the case for pairing is weak.
Why does the quantisation differ between cards for UL2?
Each card is shown running the least-compressed copy it can hold, and UL2 appears at 4 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these UL2 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 102–271 tok/s on the B200 rather than a single number.
What GPU do I need to run UL2?
The smallest card in our catalogue that holds UL2 is the Quadro K6000, with 12 GB of memory. It runs the model at Q3_K_M using about 10.5 GB, and produces roughly 14.0 tokens per second. 293 cards in total can run it.
How fast is UL2 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 169 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 248 of the cards that can run UL2 clear that.
How much VRAM does UL2 need?
About 10.5 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.
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.