UnifiedQA 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 · IQ4_XS · 19.7 tok/s
Fastest card
B200
308 tok/s · 180 GB
Which GPUs can run UnifiedQA?
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 | |||||
|---|---|---|---|---|---|---|---|
|
308
tok/s
185–493 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 12.5 GB | Q8_0 | Comfortable |
|
308
tok/s
185–493 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 12.5 GB | Q8_0 | Comfortable |
|
246
tok/s
148–394 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 12.5 GB | Q8_0 | Comfortable |
|
246
tok/s
148–394 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 12.5 GB | Q8_0 | Comfortable |
|
197
tok/s
118–315 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 12.5 GB | Q8_0 | Comfortable |
|
188
tok/s
113–301 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 12.5 GB | Q8_0 | Comfortable |
|
188
tok/s
113–301 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 12.5 GB | Q8_0 | Comfortable |
|
180
tok/s
108–288 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 12.5 GB | Q8_0 | Comfortable |
|
160
tok/s
96–256 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 12.5 GB | Q8_0 | Comfortable |
|
160
tok/s
96–256 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 12.5 GB | Q8_0 | Comfortable |
|
160
tok/s
96–256 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 12.5 GB | Q8_0 | Comfortable |
|
152
tok/s
91–243 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
141
tok/s
85–225 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 6.7 GB | IQ4_XS | Tight |
|
129
tok/s
78–207 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
107
tok/s
64–172 · low confidence |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.6 GB | Q5_K_M | Tight |
|
98.5
tok/s
59–158 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 12.5 GB | Q8_0 | Comfortable |
|
98.5
tok/s
59–158 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 12.5 GB | Q8_0 | Comfortable |
|
82.1
tok/s
49–131 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 12.5 GB | Q8_0 | Comfortable |
|
80.3
tok/s
48–129 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 12.5 GB | Q8_0 | Comfortable |
|
78.6
tok/s
47–126 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 12.5 GB | Q8_0 | Comfortable |
|
78.6
tok/s
47–126 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 12.5 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
- Allen Institute for AI,University of Washington
- Organisation type
- Research collective,Academia
- Country
- United States of America
- Published
- 2 May 2020
- Authors
- Daniel Khashabi, Sewon Min, Tushar Khot, Ashish Sabharwal, Oyvind Tafjord, Peter Clark, Hannaneh Hajishirzi
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Question answering
- Base model
- T5-11B
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
- 11B
- Training data
- tokens
- Epochs
- 1.88
- Batch size
- 27
11B from appendix A.2 : Model sizes: "Most of the experiments are done on T5(11B) which has 11 billion parameters. We also report experiments with BART (large) with 440 million parameters."
Table 2: SQuAD 1.1: 87k examples, avg total length of 136.2 + 3.0 SQuAD 2.0: 130k examples, avg total length of 139.9 + 2.6 NarrativeQA: 65k examples, avg total length of 563.6 + 6.2 RACE: 87k examples, avg total length of 317.9 + 6.9 ARC (easy): 2k examples, avg total length of 39.4 + 3.7 ARC (hard): 1k examples, avg total length of 47.4 + 5.0 OBQA: 4k examples, avg total length of 28.7 + 3.6 MCTest: 1.4k examples, avg total length of 245.4 + 4.0 BoolQ: 9k examples, avg total length of 105.1 +…
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.7 × 10¹⁹ FLOP
- How it was established
- Operation counting,Hardware
- Fine-tuning compute
- 3.8 × 10¹⁹ FLOP
A.2: "In the experiments, we use v3-8 TPUs for T5 models... pretraining UNIFIEDQA approximately takes about 36 hours on T5(11B)" (Note that v3-8 refers to 8 TPUv3 cores, or 4 TPUv3 chips. From the JAX github repo: "In a TPU v3-8 you have 4 chips, 2 cores per chip, and each core has 16GB of HBM. So this looks to JAX like 8 devices with 16GB each.") 4 * 1.23e14 * 36 * 3600 * 0.3 = 1.91e19 Alternatively, input (ouput) size of 512 (100) tokens, batch size of 8, trained for 100k steps. Input tokens…
"• Infrastructure: In the experiments, we use v3-8 TPUs for T5 models, and eight 32GB GPUs for BART models. • Time spent to build UNIFIEDQA: pretraining UNIFIEDQA approximately takes about 36 and 55 hours, on T5(11B) and BART models, respectively." 8 * 123 TFLOPS * 36 * 3600 * 0.3 (utilization assumption) = 3.8e19
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 v3
- Chips used
- 8
- Wall-clock time
- 36 hours
- Power draw
- 7.3 kW
- Compute cost
- $59
Appendix A.2: "pretraining UNIFIEDQA approximately takes about 36 and 55 hours, on T5(11B) and BART models, respectively."
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
- Hugging Face
- allenai
Apache 2.0 license, includes models and training code: https://github.com/allenai/unifiedqa
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
- 816
Table 5 "We then introduce UNIFIEDQA (§3.2) that is a QA system trained on datasets in multiple formats, indicating new state-of-the-art results on 10 datasets and generalization to unseen datasets."
Sources
Where this record came from and when it was last checked.
- Reference
- UnifiedQA: Crossing Format Boundaries With a Single QA System
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run UnifiedQA
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 308 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 308 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 246 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 246 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 197 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 188 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 188 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 180 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 160 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 160 tok/s
The smallest GPUs that still run UnifiedQA
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 6.7 GB · IQ4_XS · tight 21.2 tok/s
- 02 Radeon RX 9060 8 GB · needs 6.7 GB · IQ4_XS · tight 23.8 tok/s
- 03 GeForce RTX 5050 8 GB · needs 6.7 GB · IQ4_XS · tight 30.3 tok/s
- 04 GeForce RTX 5050 Mobile 8 GB · needs 6.7 GB · IQ4_XS · tight 36.3 tok/s
- 05 Radeon RX 9060 XT 8 GB 8 GB · needs 6.7 GB · IQ4_XS · tight 23.8 tok/s
- 06 GeForce RTX 5060 Mobile 8 GB · needs 6.7 GB · IQ4_XS · tight 36.3 tok/s
- 07 GeForce RTX 5060 8 GB · needs 6.7 GB · IQ4_XS · tight 42.4 tok/s
- 08 GeForce RTX 5060 Ti 8 GB 8 GB · needs 6.7 GB · IQ4_XS · tight 42.4 tok/s
- 09 GeForce RTX 5070 Mobile 8 GB · needs 6.7 GB · IQ4_XS · tight 36.3 tok/s
- 10 Radeon RX 7650 GRE 8 GB · needs 6.7 GB · IQ4_XS · tight 21.2 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Xeon Phi 5110P
Memory needed
6.7 GB
Fastest
308 tok/s
UnifiedQA reaches a parameter count of 11B. That is small enough that hardware is rarely the obstacle, including on cards several years old. The number of cards we track that can run it: 509.
The smallest card that holds it is Xeon Phi 5110P, with a memory capacity of 8 GB, running it at a compression of IQ4_XS and producing around 19.7 tokens per second.
At the other end sits B200, generating roughly 308 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
UnifiedQA was published by Allen Institute for AI,University of Washington, in the country recorded as United States of America, during May 2020. The publishing organisation is categorised as research collective,Academia.
It works in the domain of Language, and is recorded as performing the task of question answering.
Rather than being trained from scratch, it is derived from T5-11B. Most models at this scale are adapted from an existing base rather than built from nothing.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. On Hugging Face it is published under the organisation allenai.
How fast it runs, and why
The median result is around 21.2 tokens per second. Exceeding reading speed outright: 460 of them.
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.
What went into building it
The training run consumed about 1.7 × 10¹⁹ FLOP, on hardware recorded as Google TPU v3. That figure measures what producing the model cost, and has no bearing on how fast it answers.
It is tracked in the underlying dataset for one reason in particular: sOTA improvement.
Step by step
How to choose a GPU for UnifiedQA
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
Start from what it actually needs, which is the requirement of UnifiedQA, needing around 6.7 GB at a compression of IQ4_XS. No amount of processing power compensates for a card that cannot hold it.
-
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 a card that seemed fine stops fitting UnifiedQA.
-
03
Decide how much compression you will accept
The quantisation column varies by card, because a bigger card holds a more accurate copy, reaching a compression of IQ4_XS on the smallest card that fits. Setting a minimum quality drops the cards that only manage it by squeezing further than you would want, and holds the comparison at one level.
-
04
Sort by speed
Ranking by tokens per second follows memory bandwidth rather than core counts, for UnifiedQA. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 308 tok/s.
-
05
Read the fit column last
Tight means it loads and works with no room to raise the context later, in the case of UnifiedQA. Comfortable means you can grow the context later. That difference matters more than a few tokens per second, so buy for comfortable if you expect to.
-
06
Open the card you have settled on
Every card name links to its own page, which runs the same calculation across the whole model catalogue. A card is usually bought for more than one model, so it is worth a look before buying for UnifiedQA.
Answers
UnifiedQA — common questions
UnifiedQA— how much compute was used to train it?
Training consumed around 1.7 × 10¹⁹ FLOP, on hardware recorded as Google TPU v3. 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.
UnifiedQA— can I run it if it does not fit in my GPU?
It can be split between the card and system memory, but it generates painfully slowly that way. The nearest miss we calculate falls short by 2.0 GB. Every figure here assumes the whole model is resident on the card.
UnifiedQA— would two GPUs run it faster?
A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 509. So a second card is rarely the answer here.
UnifiedQA— why does the quantisation differ between cards?
A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
UnifiedQA— how accurate are these speed estimates?
These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 185–493 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
UnifiedQA— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Xeon Phi 5110P, with a memory capacity of 8 GB. It runs the model at a compression of IQ4_XS using about 6.7 GB, and produces roughly 19.7 tokens per second. The number of cards able to run it in total: 509.
UnifiedQA— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 308 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and the number of cards clearing that: 460.
UnifiedQA— how much VRAM does it need?
It needs about 6.7 GB at a compression of IQ4_XS, 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.
UnifiedQA— can I run it on a GPU holding 8 GB?
Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of IQ4_XS, using about 6.7 GB and generating roughly 141 tokens per second. The fit is tight.
UnifiedQA— can I run it on a GPU holding 12 GB?
Yes. The card GeForce RTX 3080 Ti, holding 12 GB, runs it at a compression of Q6_K, using about 9.9 GB and generating roughly 51.0 tokens per second. The fit is tight.
UnifiedQA— can I run it on a GPU holding 16 GB?
Yes. The card Tesla V100 SXM2 16 GB, holding 16 GB, runs it at a compression of Q8_0, using about 12.5 GB and generating roughly 43.5 tokens per second. The fit is tight.
UnifiedQA— can I run it on a GPU holding 24 GB?
Yes. The card GeForce RTX 5090 D V2, holding 24 GB, runs it at a compression of Q8_0, using about 12.5 GB and generating roughly 51.6 tokens per second. The fit is comfortable.
UnifiedQA— is it open source?
Its weights are published, so it 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.
UnifiedQA— how many parameters does it have?
It has a parameter count of 11B. 11B from appendix A.2 : Model sizes: "Most of the experiments are done on T5(11B) which has 11 billion parameters. We also report experiments with BART (large) with 440 million parameters.". 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.
UnifiedQA— who created it?
It was published by Allen Institute for AI,University of Washington, based in United States of America, an organisation categorised as research collective,Academia.
UnifiedQA— when was it released?
It was published in May 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.
UnifiedQA— what is it used for?
It works in the domain of Language, and is recorded as handling the task of question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
UnifiedQA— where can I download it?
Its weights are published on Hugging Face, under the organisation allenai. We do not host model files — this site calculates what hardware is needed to run them.
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.