OLMo 2 32B TPS calculator

Open weights Allen Institute for AI 32B parameters March 2025

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

132 cards that can run it

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 2 32B?

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
13 March 2025

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
32B

32B

Training data
4,000,000,000,000 tokens

"It is trained up to 6T tokens and post-trained using Tulu 3.1." "OLMo 2 32B is trained for 1.5 epochs, up to 6T tokens" Pretraining Stage 1 (OLMo-Mix-1124) 6T tokens ( = 1.5 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)

Epochs
1.5

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.3 × 10²⁴ FLOP

first table here: https://allenai.org/blog/olmo2-32B

How it was established
Reported

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
Hardware utilisation
MFU 38.0%

"Training infrastructure: OLMo 2 32B was trained on Augusta, a 160 node AI Hypercomputer provided by Google Cloud Engine. Each node has 8 H100 GPUs, and the nodes are connected with GPUDirect-TCPXO interconnect. Over the course of the training run, we reached performance of over 1800 tokens per second per GPU (~38% MFU)."

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 https://huggingface.co/allenai/OLMo-2-0325-32B (base) allenai/OLMo-2-0325-32B-Instruct (base+SFT+DPO+RVLR) Apache 2.0 https://github.com/allenai/OLMo-core

Hugging Face
allenai

How it is classified

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

Record confidence
Confident

Sources

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

Reference
OLMo 2 32B: First fully open model to outperform GPT 3.5 and GPT 4o mini
Last updated
28 November 2025

The extremes

What the numbers mean

What it takes to run this model

Minimum card

RTX A4500

Memory needed

16.3 GB

Fastest

106 tok/s

OLMo 2 32B 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 smallest card that holds it 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.

The fastest we calculate for it is B200, generating roughly 106 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

About this model

OLMo 2 32B was published by Allen Institute for AI, in the country recorded as United States of America, during March 2025. The category the publisher falls under is research collective.

It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Question answering.

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. On Hugging Face it is published under the organisation allenai.

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.

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.

What went into building it

Producing it required arithmetic totalling around 1.3 × 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.

The training set ran to roughly 4,000,000,000,000 tokens of text.

Step by step

How to choose a GPU for OLMo 2 32B

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

  1. 01

    Start from the memory column

    The table lists every card able to hold OLMo 2 32B, needing around 16.3 GB at a compression of Q3_K_M. That figure, not the headline performance of a card, is what decides whether it runs.

  2. 02

    Decide how long your conversations run

    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 2 32B.

  3. 03

    Choose how far you will compress it

    The quantisation column varies by card, because a bigger card holds a more accurate copy, 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.

  4. 04

    Rank by throughput rather than spec sheet

    The speed ordering is effectively an ordering by memory bandwidth, for OLMo 2 32B. 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.

  5. 05

    Check the fit verdict before buying

    Tight means it loads and works with no room to raise the context later, in the case of OLMo 2 32B. 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.

  6. 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 OLMo 2 32B.

Answers

OLMo 2 32B — common questions

01

OLMo 2 32B— 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.

02

OLMo 2 32B— 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.

03

OLMo 2 32B— 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.

04

OLMo 2 32B— how accurate are these speed estimates?

They are calculated from specifications rather than measured, and each carries a range. One example: 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.

05

OLMo 2 32B— 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.

06

OLMo 2 32B— 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.

07

OLMo 2 32B— 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.

08

OLMo 2 32B— 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.

09

OLMo 2 32B— 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.

10

OLMo 2 32B— how many parameters does it have?

It has a parameter count of 32B. 32B. 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.

11

OLMo 2 32B— who created it?

It was published by Allen Institute for AI, based in United States of America, an organisation categorised as research collective.

12

OLMo 2 32B— when was it released?

It was published in March 2025.

13

OLMo 2 32B— what is it used for?

It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

14

OLMo 2 32B— 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.

15

OLMo 2 32B— how much compute was used to train it?

Training consumed around 1.3 × 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.

Source

Original publication

Record last updated 28 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.