OLMo 2 Furious 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
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 OLMo 2 Furious 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
- Allen Institute for AI,University of Washington,New York University (NYU)
- Organisation type
- Research collective,Academia,Academia
- Country
- United States of America
- Published
- 31 December 2024
- Authors
- Team OLMo, Pete Walsh, Luca Soldaini, Dirk Groeneveld, Kyle Lo, Shane Arora, Akshita Bhagia, Yuling Gu, Shengyi Huang, Matt Jordan, Nathan Lambert, Dustin Schwenk, Oyvind Tafjord, Taira Anderson, David Atkinson, Faeze Brahman, Christopher Clark, Pradeep Dasigi, Nouha Dziri, Michal Guerquin, Hamish Ivison, Pang Wei Koh, Jiacheng Liu, Saumya Malik, William Merrill, Lester James V. Miranda, Jacob Mor…
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
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
- tokens
- Epochs
- 1.2
13B
Pretraining Stage 1 (OLMo-Mix-1124) 5 trillion tokens ( = 1.2 epochs) Pretraining Stage 2 (Dolmino-Mix-1124) 100B tokens (3 runs) 300B tokens (1 run) merged Post-training (Tulu 3 SFT OLMo mix) SFT + DPO + PPO (preference mix)
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
- 4.6 × 10²³ FLOP
- How it was established
- Reported,Operation counting
4.6*10^23 FLOPs (Table 6 - developers calculated using 6ND formula)
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
- Chip-hours
- 1,280
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 https://huggingface.co/allenai/OLMo-2-1124-13B https://github.com/allenai/OLMo
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Likely above 10²³ FLOP
- Yes
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- 2 OLMo 2 Furious
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs for OLMo 2 Furious 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 OLMo 2 Furious 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
What you need to run it
Minimum card
Xeon Phi 5110P
Memory needed
7.1 GB
Fastest
261 tok/s
OLMo 2 Furious 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.
The least hardware that works is a Xeon Phi 5110P. Its 8 GB is enough at Q3_K_M compression, giving roughly 18.3 tokens per second.
The quickest result comes from a B200 at around 261 tokens per second — its 8,000 GB/s of bandwidth is what buys that.
Background
OLMo 2 Furious 13B was published by Allen Institute for AI,University of Washington,New York University (NYU), in United States of America, in December 2024. The organisation is categorised as research collective,Academia,Academia.
It works in Language, and is recorded as doing language modeling/generation, Question answering.
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. It is published under the allenai organisation on Hugging Face.
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.
Training and provenance
Producing it required around 4.6 × 10²³ FLOP of arithmetic, on NVIDIA H100 SXM5 80GB, which is a statement about the training budget rather than about inference.
Step by step
How to choose a GPU for OLMo 2 Furious 13B
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
Look at what OLMo 2 Furious 13B actually needs — around 7.1 GB at Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
-
02
Decide how long your conversations run
The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context OLMo 2 Furious 13B can slip off a card that handles short questions easily.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold — Q3_K_M on the smallest card that fits. Setting a floor drops the cards that only manage OLMo 2 Furious 13B by squeezing it further than you would want.
-
04
Compare tokens per second, not specifications
The speed ordering for OLMo 2 Furious 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 OLMo 2 Furious 13B but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
06
See what else that card runs
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond OLMo 2 Furious 13B.
Answers
OLMo 2 Furious 13B — common questions
Is OLMo 2 Furious 13B open source?
Its weights are published, so OLMo 2 Furious 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 OLMo 2 Furious 13B have?
OLMo 2 Furious 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 OLMo 2 Furious 13B?
OLMo 2 Furious 13B was published by Allen Institute for AI,University of Washington,New York University (NYU), based in United States of America, categorised as research collective,Academia,Academia.
When was OLMo 2 Furious 13B released?
OLMo 2 Furious 13B was published in December 2024. 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 OLMo 2 Furious 13B used for?
OLMo 2 Furious 13B works in Language, and is recorded as handling language modeling/generation, Question answering. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.
Where can I download OLMo 2 Furious 13B?
Its weights are published under the allenai 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 OLMo 2 Furious 13B?
Around 4.6 × 10²³ FLOP, on 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.
Can I run OLMo 2 Furious 13B if it does not fit in my GPU?
It can be split between the card and system memory, but OLMo 2 Furious 13B generates painfully slowly that way — the nearest miss we calculate is short by 3.2 GB. Nothing on this page assumes offloading.
Would two GPUs run OLMo 2 Furious 13B faster?
A second card roughly doubles the memory available but not the generation rate. With 509 cards already able to run OLMo 2 Furious 13B alone, the case for pairing is weak.
Why does the quantisation differ between cards for OLMo 2 Furious 13B?
Each card is shown running the least-compressed copy it can hold, and OLMo 2 Furious 13B appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these OLMo 2 Furious 13B 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 156–417 tok/s on the B200 rather than a single number.
What GPU do I need to run OLMo 2 Furious 13B?
The smallest card in our catalogue that holds OLMo 2 Furious 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 OLMo 2 Furious 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 OLMo 2 Furious 13B clear that.
How much VRAM does OLMo 2 Furious 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 OLMo 2 Furious 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 OLMo 2 Furious 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 OLMo 2 Furious 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 OLMo 2 Furious 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.