Qwen2.5-32B 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.5 tok/s
Fastest card
B200
104 tok/s · 180 GB
Which GPUs can run Qwen2.5-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 | |||||
|---|---|---|---|---|---|---|---|
|
104
tok/s
89–125 |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 35.5 GB | Q8_0 | Comfortable |
|
104
tok/s
89–125 |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 35.5 GB | Q8_0 | Comfortable |
|
83.3
tok/s
50–133 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 35.5 GB | Q8_0 | Comfortable |
|
83.3
tok/s
50–133 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 35.5 GB | Q8_0 | Comfortable |
|
66.6
tok/s
40–107 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 35.5 GB | Q8_0 | Comfortable |
|
63.7
tok/s
54–76 |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 35.5 GB | Q8_0 | Comfortable |
|
63.7
tok/s
54–76 |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 35.5 GB | Q8_0 | Comfortable |
|
61.0
tok/s
37–98 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 35.5 GB | Q8_0 | Comfortable |
|
54.1
tok/s
32–87 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 35.5 GB | Q8_0 | Comfortable |
|
54.1
tok/s
32–87 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 35.5 GB | Q8_0 | Comfortable |
|
54.1
tok/s
32–87 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 35.5 GB | Q8_0 | Comfortable |
|
51.3
tok/s
44–62 |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 35.5 GB | Q8_0 | Comfortable |
|
43.8
tok/s
37–53 |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 35.5 GB | Q8_0 | Comfortable |
|
43.8
tok/s
37–53 |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 35.5 GB | Q8_0 | Comfortable |
|
43.8
tok/s
37–53 |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 35.5 GB | Q8_0 | Comfortable |
|
43.8
tok/s
37–53 |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 35.5 GB | Q8_0 | Comfortable |
|
43.8
tok/s
37–53 |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 35.5 GB | Q8_0 | Comfortable |
|
40.3
tok/s
34–48 |
GeForce RTX 5090 D V2 NVIDIA | 24 GB | 1,340 GB/s | Aug 2025 | 20.3 GB | Q4_K_M | Tight |
|
36.7
tok/s
31–44 |
A30X NVIDIA | 24 GB | 1,220 GB/s | Apr 2021 | 20.3 GB | Q4_K_M | Tight |
|
35.4
tok/s
30–42 |
DRIVE A100 PROD NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 27.9 GB | Q6_K | Tight |
|
35.4
tok/s
30–42 |
GRID A100A NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 27.9 GB | Q6_K | Tight |
|
33.9
tok/s
29–41 |
GeForce RTX 5090 NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 27.9 GB | Q6_K | Tight |
|
33.9
tok/s
29–41 |
GeForce RTX 5090 D NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 27.9 GB | Q6_K | Tight |
|
33.3
tok/s
20–53 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 35.5 GB | Q8_0 | Comfortable |
|
33.3
tok/s
20–53 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 35.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
- Alibaba
- Organisation type
- Industry
- Country
- China
- Published
- 17 September 2024
- Authors
- Qwen Team
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, Quantitative reasoning
- 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
- 32.5B
- Training data
- 18,000,000,000,000 tokens
- Epochs
- 1
32.5B
"In terms of Qwen2.5, the language models, all models are pretrained on our latest large-scale dataset, encompassing up to 18 trillion tokens"
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
- 3.5 × 10²⁴ FLOP
- How it was established
- Operation counting
6 FLOP / parameter / token * 32.5B parameters * 18 trillion tokens = 3.51 × 10^24 FLOP
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
- Qwen
Apache 2.0 https://huggingface.co/Qwen/Qwen2.5-32B
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
- Why it is tracked
- Training cost
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- Qwen2.5: A Party of Foundation Models!
- Last updated
- 18 December 2025
The extremes
The ten fastest GPUs that run Qwen2.5-32B
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 104 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 104 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 83.3 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 83.3 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 66.6 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 63.7 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 63.7 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 61.0 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 54.1 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 54.1 tok/s
The smallest GPUs that still run Qwen2.5-32B
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.5 GB · Q3_K_M · tight 12.7 tok/s
- 02 RTX 4000 SFF Ada Generation 20 GB · needs 16.5 GB · Q3_K_M · tight 9.9 tok/s
- 03 Radeon RX 7900 XT 20 GB · needs 16.5 GB · Q3_K_M · tight 21.9 tok/s
- 04 A10M 20 GB · needs 16.5 GB · Q3_K_M · tight 17.6 tok/s
- 05 GeForce RTX 3080 Ti 20 GB 20 GB · needs 16.5 GB · Q3_K_M · tight 26.7 tok/s
- 06 RTX A4500 20 GB · needs 16.5 GB · Q3_K_M · tight 22.5 tok/s
- 07 Arc Pro B60 24 GB · needs 20.3 GB · Q4_K_M · tight 8.9 tok/s
- 08 GeForce RTX 5090 D V2 24 GB · needs 20.3 GB · Q4_K_M · tight 40.3 tok/s
- 09 RTX PRO 4000 Blackwell SFF 24 GB · needs 20.3 GB · Q4_K_M · tight 13.0 tok/s
- 10 GeForce RTX 5090 Mobile 24 GB · needs 20.3 GB · Q4_K_M · tight 27.0 tok/s
What the numbers mean
What you need to run it
Minimum card
RTX A4500
Memory needed
16.5 GB
Fastest
104 tok/s
Qwen2.5-32B reaches a parameter count of 32.5B. 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.5 tokens per second.
The quickest result comes from B200, generating roughly 104 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
Qwen2.5-32B was published by Alibaba, in the country recorded as China, during September 2024. The publishing organisation is categorised as industry.
It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Question answering, Quantitative reasoning.
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 Qwen.
How fast it runs, and why
Half the cards that hold it manage more than 20.3 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 102 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 attention layout is on file, so the memory figures are computed exactly rather than approximated.
What went into building it
The training run consumed about 3.5 × 10²⁴ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The training set ran to roughly 18,000,000,000,000 tokens of text.
Its inclusion criterion: training cost.
Step by step
How to choose a GPU for Qwen2.5-32B
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
Every card here has been checked against Qwen2.5-32B, needing around 16.5 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 Qwen2.5-32B.
-
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.
-
04
Rank by throughput rather than spec sheet
The speed ordering is effectively an ordering by memory bandwidth, for Qwen2.5-32B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 104 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 Qwen2.5-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.
-
06
See what else that card runs
Following a card through to its own page shows every other model it can hold, which is the question that follows once you have settled on Qwen2.5-32B.
Answers
Qwen2.5-32B — common questions
Qwen2.5-32B— who created it?
It was published by Alibaba, based in China, an organisation categorised as industry.
Qwen2.5-32B— when was it released?
It was published in September 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.
Qwen2.5-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, Quantitative reasoning. These are the areas it was designed around; they describe intent rather than a hard boundary.
Qwen2.5-32B— where can I download it?
Its weights are published on Hugging Face, under the organisation Qwen. We do not host model files — this site calculates what hardware is needed to run them.
Qwen2.5-32B— how much compute was used to train it?
Training consumed around 3.5 × 10²⁴ FLOP. 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.
Qwen2.5-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.9 GB. Every figure here assumes the whole model is resident on the card.
Qwen2.5-32B— would two GPUs run it faster?
Capacity adds across cards; throughput does not. The number of cards already holding it on their own: 132. So a second card is rarely the answer here.
Qwen2.5-32B— 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: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Qwen2.5-32B— 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: 89–125 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Qwen2.5-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.5 GB, and produces roughly 22.5 tokens per second. The number of cards able to run it in total: 132.
Qwen2.5-32B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 104 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: 102.
Qwen2.5-32B— how much VRAM does it need?
It needs about 16.5 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.
Qwen2.5-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.3 GB and generating roughly 40.3 tokens per second. The fit is tight.
Qwen2.5-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.
Qwen2.5-32B— how many parameters does it have?
It has a parameter count of 32.5B. 32.5B. 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.
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.