Olmo 3 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
RTX A4500
20 GB · Q3_K_M · 22.9 tok/s
Fastest card
B200
106 tok/s · 180 GB
Which GPUs can run Olmo 3?
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.
132 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
106
tok/s
64–169 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 35.0 GB | Q8_0 | Comfortable |
|
106
tok/s
64–169 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 35.0 GB | Q8_0 | Comfortable |
|
84.6
tok/s
51–135 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 35.0 GB | Q8_0 | Comfortable |
|
84.6
tok/s
51–135 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 35.0 GB | Q8_0 | Comfortable |
|
67.6
tok/s
41–108 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 35.0 GB | Q8_0 | Comfortable |
|
64.7
tok/s
39–104 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 35.0 GB | Q8_0 | Comfortable |
|
64.7
tok/s
39–104 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 35.0 GB | Q8_0 | Comfortable |
|
61.9
tok/s
37–99 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 35.0 GB | Q8_0 | Comfortable |
|
55.0
tok/s
33–88 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 35.0 GB | Q8_0 | Comfortable |
|
55.0
tok/s
33–88 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 35.0 GB | Q8_0 | Comfortable |
|
55.0
tok/s
33–88 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 35.0 GB | Q8_0 | Comfortable |
|
52.2
tok/s
31–83 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
40.9
tok/s
25–66 · low confidence |
GeForce RTX 5090 D V2 NVIDIA | 24 GB | 1,340 GB/s | Aug 2025 | 20.1 GB | Q4_K_M | Tight |
|
37.3
tok/s
22–60 · low confidence |
A30X NVIDIA | 24 GB | 1,220 GB/s | Apr 2021 | 20.1 GB | Q4_K_M | Tight |
|
36.0
tok/s
22–58 · low confidence |
DRIVE A100 PROD NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 27.5 GB | Q6_K | Tight |
|
36.0
tok/s
22–58 · low confidence |
GRID A100A NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 27.5 GB | Q6_K | Tight |
|
34.4
tok/s
21–55 · low confidence |
GeForce RTX 5090 NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 27.5 GB | Q6_K | Tight |
|
34.4
tok/s
21–55 · low confidence |
GeForce RTX 5090 D NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 27.5 GB | Q6_K | Tight |
|
33.9
tok/s
20–54 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 35.0 GB | Q8_0 | Comfortable |
|
33.9
tok/s
20–54 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 35.0 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
- Organisation type
- Research collective
- Country
- United States of America
- Published
- 20 November 2025
- Authors
- Allyson Ettinger, Amanda Bertsch, Bailey Kuehl, David Graham, David Heineman, Dirk Groeneveld, Faeze Brahman, Finbarr Timbers, Hamish Ivison, Jacob Morrison, Jake Poznanski, Kyle Lo, Luca Soldaini, Matt Jordan, Mayee Chen, Michael Noukhovitch, Nathan Lambert, Pete Walsh, Pradeep Dasigi, Robert Berry, Saumya Malik, Saurabh Shah, Scott Geng, Shane Arora, Shashank Gupta, Taira Anderson, Teng Xiao, Ty…
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Chat, Reasoning, Code generation
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
- 32B
- Training data
- 5,500,000,000,000 tokens
- Epochs
- 1
32B with Base/Instruct/Think variants. Base here
Model card lists 5.50T training tokens for OLMo 3 32B (and 5.93T for 7B).
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.1 × 10²⁴ FLOP
6*3.2e10*5.5e12=1.1e24
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
- NVIDIA H100 SXM5 80GB
- Chips used
- 1,024
- Wall-clock time
- 1,344 hours (56 days)
- Power draw
- 1.4 MW
In total, approximately 56 days elapsed from the start of training to the evaluation of the Olmo 3 Think 32B checkpoint, on a cluster with 1024 H100 GPUs dedicated to Olmo 3
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
Model card + artifacts: https://allenai.org/olmo and https://huggingface.co/allenai/Olmo-3-1125-32B (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
Paper/technical report describes Olmo 3 Think 32B as the strongest fully-open thinking model released to date.
Sources
Where this record came from and when it was last checked.
- Reference
- Olmo 3
- Last updated
- 31 March 2026
The extremes
The ten fastest GPUs that run Olmo 3
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 106 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 106 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 84.6 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 84.6 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 67.6 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 64.7 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 64.7 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 61.9 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 55.0 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 55.0 tok/s
The smallest GPUs that still run Olmo 3
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 RTX 4000 Ada Generation 20 GB · needs 16.3 GB · Q3_K_M · tight 12.9 tok/s
- 02 RTX 4000 SFF Ada Generation 20 GB · needs 16.3 GB · Q3_K_M · tight 10.0 tok/s
- 03 Radeon RX 7900 XT 20 GB · needs 16.3 GB · Q3_K_M · tight 22.3 tok/s
- 04 A10M 20 GB · needs 16.3 GB · Q3_K_M · tight 17.9 tok/s
- 05 GeForce RTX 3080 Ti 20 GB 20 GB · needs 16.3 GB · Q3_K_M · tight 27.2 tok/s
- 06 RTX A4500 20 GB · needs 16.3 GB · Q3_K_M · tight 22.9 tok/s
- 07 Arc Pro B60 24 GB · needs 20.1 GB · Q4_K_M · tight 9.1 tok/s
- 08 GeForce RTX 5090 D V2 24 GB · needs 20.1 GB · Q4_K_M · tight 40.9 tok/s
- 09 RTX PRO 4000 Blackwell SFF 24 GB · needs 20.1 GB · Q4_K_M · tight 13.2 tok/s
- 10 GeForce RTX 5090 Mobile 24 GB · needs 20.1 GB · Q4_K_M · tight 27.4 tok/s
What the numbers mean
What you need to run it
Minimum card
RTX A4500
Memory needed
16.3 GB
Fastest
106 tok/s
Olmo 3 reaches a parameter count of 32B. That lands in the range a serious desktop card can handle once the weights are compressed. The number of cards we track that can run it: 132.
The least hardware that works is RTX A4500, with a memory capacity of 20 GB, running it at a compression of Q3_K_M and producing around 22.9 tokens per second.
Top of the range is B200, generating roughly 106 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
Olmo 3 was published by Allen Institute for AI, in the country recorded as United States of America, during November 2025. It comes out of an organisation categorised as research collective.
It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Chat, Reasoning, Code generation.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.
How fast it runs, and why
Across every card that can run it, the middle of the range sits at 20.7 tokens per second. Exceeding reading speed outright: 103 of them.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
Without the attention layout on record, the memory column is an approximation. It is close enough to choose hardware by, and least reliable at long context.
What went into building it
Producing it required arithmetic totalling around 1.1 × 10²⁴ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. That figure measures what producing the model cost, and has no bearing on how fast it answers.
It was trained on a corpus of about 5,500,000,000,000 tokens of text.
It is tracked in the underlying dataset for one reason in particular: sOTA improvement.
Step by step
How to choose a GPU for Olmo 3
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
Start from what it actually needs, which is the requirement of Olmo 3, needing around 16.3 GB at a compression of Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
-
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 a card that seemed fine stops fitting Olmo 3.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold, reaching a compression of Q3_K_M 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
Rank by throughput rather than spec sheet
Ranking by tokens per second follows memory bandwidth rather than core counts, for Olmo 3. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 106 tok/s.
-
05
Look at the headroom, not just the fit
The fit column separates cards that just manage it from those with room to spare, in the case of Olmo 3. 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
Check the card from the other side
Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond Olmo 3.
Answers
Olmo 3 — common questions
Olmo 3— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Chat, Reasoning, Code generation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Olmo 3— where can I download it?
The weights are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Olmo 3— how much compute was used to train it?
Training consumed around 1.1 × 10²⁴ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. 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.
Olmo 3— can I run it if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part held in system memory drags the whole thing down. The nearest miss we calculate falls short by 5.7 GB. Every figure here assumes the whole model is resident on the card.
Olmo 3— would two GPUs run it faster?
Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 132. So a second card is rarely the answer here.
Olmo 3— why does the quantisation differ between cards?
Each card is shown running the least-compressed copy it can hold. The number of distinct compression levels across the cards that fit it: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Olmo 3— 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: 64–169 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Olmo 3— what GPU do I need to run it?
The smallest card in our catalogue that holds it is RTX A4500, with a memory capacity of 20 GB. It runs the model at a compression of Q3_K_M using about 16.3 GB, and produces roughly 22.9 tokens per second. The number of cards able to run it in total: 132.
Olmo 3— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 106 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: 103.
Olmo 3— how much VRAM does it need?
It needs about 16.3 GB at a compression of Q3_K_M, 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.
Olmo 3— 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 Q4_K_M, using about 20.1 GB and generating roughly 40.9 tokens per second. The fit is tight.
Olmo 3— 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.
Olmo 3— how many parameters does it have?
It has a parameter count of 32B. 32B with Base/Instruct/Think variants. Base here. 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.
Olmo 3— who created it?
It was published by Allen Institute for AI, based in United States of America, an organisation categorised as research collective.
Olmo 3— when was it released?
It was published in November 2025.
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.