DeepSeek-R1-Distill-Qwen-14B 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
P102-101
10 GB · Q3_K_M · 21.0 tok/s
Fastest card
B200
229 tok/s · 180 GB
Which GPUs can run DeepSeek-R1-Distill-Qwen-14B?
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.
306 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
229
tok/s
195–275 |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 17.1 GB | Q8_0 | Comfortable |
|
229
tok/s
195–275 |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 17.1 GB | Q8_0 | Comfortable |
|
183
tok/s
110–293 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 17.1 GB | Q8_0 | Comfortable |
|
183
tok/s
110–293 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 17.1 GB | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 17.1 GB | Q8_0 | Comfortable |
|
140
tok/s
119–168 |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 17.1 GB | Q8_0 | Comfortable |
|
140
tok/s
119–168 |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 17.1 GB | Q8_0 | Comfortable |
|
134
tok/s
80–214 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 17.1 GB | Q8_0 | Comfortable |
|
120
tok/s
102–145 |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.5 GB | Q3_K_M | Tight |
|
119
tok/s
71–190 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 17.1 GB | Q8_0 | Comfortable |
|
119
tok/s
71–190 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 17.1 GB | Q8_0 | Comfortable |
|
119
tok/s
71–190 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 17.1 GB | Q8_0 | Comfortable |
|
113
tok/s
96–135 |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 17.1 GB | Q8_0 | Comfortable |
|
96.2
tok/s
82–115 |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 17.1 GB | Q8_0 | Comfortable |
|
96.2
tok/s
82–115 |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 17.1 GB | Q8_0 | Comfortable |
|
96.2
tok/s
82–115 |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 17.1 GB | Q8_0 | Comfortable |
|
96.2
tok/s
82–115 |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 17.1 GB | Q8_0 | Comfortable |
|
96.2
tok/s
82–115 |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 17.1 GB | Q8_0 | Comfortable |
|
73.2
tok/s
44–117 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 17.1 GB | Q8_0 | Comfortable |
|
73.2
tok/s
44–117 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 17.1 GB | Q8_0 | Comfortable |
|
61.0
tok/s
37–98 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 17.1 GB | Q8_0 | Comfortable |
|
60.3
tok/s
51–72 |
GeForce RTX 3080 12 GB NVIDIA | 12 GB | 912 GB/s | Jan 2022 | 10.2 GB | Q4_K_M | Tight |
|
60.3
tok/s
51–72 |
GeForce RTX 3080 Ti NVIDIA | 12 GB | 912 GB/s | May 2021 | 10.2 GB | Q4_K_M | Tight |
|
59.7
tok/s
36–96 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 17.1 GB | Q8_0 | Comfortable |
|
58.7
tok/s
50–70 |
CMP 90HX NVIDIA | 10 GB | 760 GB/s | Jul 2021 | 8.5 GB | Q3_K_M | Tight |
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
- DeepSeek
- Organisation type
- Industry
- Country
- China
- Published
- 22 January 2025
- Authors
- DeepSeek-AI, Daya Guo, Dejian Yang, Haowei Zhang, Junxiao Song, Ruoyu Zhang, Runxin Xu, Qihao Zhu, Shirong Ma, Peiyi Wang, Xiao Bi, Xiaokang Zhang, Xingkai Yu, Yu Wu, Z.F. Wu, Zhibin Gou, Zhihong Shao, Zhuoshu Li, Ziyi Gao, Aixin Liu, Bing Xue, Bingxuan Wang, Bochao Wu, Bei Feng, Chengda Lu, Chenggang Zhao, Chengqi Deng, Chenyu Zhang, Chong Ruan, Damai Dai, Deli Chen, Dongjie Ji, Erhang Li, Fangyu…
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Quantitative reasoning, Question answering, Mathematical reasoning, Code generation
- Base model
- Qwen2.5-14B
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
- 14.8B
- Training data
- 24,000,000,000 tokens
- Epochs
- 2
14.8B (safetensors)
"finetuned with 800k samples curated with DeepSeek-R1" assuming ~30000 tokens per sample 30000 * 800000 = 24 000 000 000 tokens (speculative)
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.
- How it was established
- Operation counting
- Fine-tuning compute
- 4.3 × 10²¹ FLOP
6 FLOP / token / parameter * 14.8 * 10^9 parameters * 24 * 10^9 tokens * 2 epochs = 4.2624e+21 FLOP (speculative since number of tokens could be +- 1 OOM)
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
- deepseek-ai
https://huggingface.co/deepseek-ai/DeepSeek-R1-Distill-Qwen-14B MIT license
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Speculative
Sources
Where this record came from and when it was last checked.
- Reference
- DeepSeek-R1: Incentivizing Reasoning Capability in LLMs via Reinforcement Learning
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run DeepSeek-R1-Distill-Qwen-14B
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 229 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 229 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 183 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 183 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 146 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 140 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 140 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 134 tok/s
- 09 CMP 170HX 10 GB 10 GB · 1,560 GB/s · Q3_K_M 120 tok/s
- 10 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 119 tok/s
The smallest GPUs that still run DeepSeek-R1-Distill-Qwen-14B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Arc B570 10 GB · needs 8.5 GB · Q3_K_M · tight 19.1 tok/s
- 02 Xbox Series X 6nm GPU 10 GB · needs 8.5 GB · Q3_K_M · tight 33.7 tok/s
- 03 Radeon RX 6750 GRE 10 GB 10 GB · needs 8.5 GB · Q3_K_M · tight 19.3 tok/s
- 04 CMP 170HX 10 GB 10 GB · needs 8.5 GB · Q3_K_M · tight 120 tok/s
- 05 CMP 90HX 10 GB · needs 8.5 GB · Q3_K_M · tight 58.7 tok/s
- 06 CMP 50HX 10 GB · needs 8.5 GB · Q3_K_M · tight 43.2 tok/s
- 07 Radeon RX 6700 10 GB · needs 8.5 GB · Q3_K_M · tight 19.3 tok/s
- 08 Radeon RX 6700M 10 GB · needs 8.5 GB · Q3_K_M · tight 19.3 tok/s
- 09 Xbox Series X GPU 10 GB · needs 8.5 GB · Q3_K_M · tight 33.7 tok/s
- 10 GeForce RTX 3080 10 GB · needs 8.5 GB · Q3_K_M · tight 58.7 tok/s
What the numbers mean
What you need to run it
Minimum card
P102-101
Memory needed
8.5 GB
Fastest
229 tok/s
DeepSeek-R1-Distill-Qwen-14B reaches a parameter count of 14.8B. 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: 306.
The least hardware that works is P102-101, with a memory capacity of 10 GB, running it at a compression of Q3_K_M and producing around 21.0 tokens per second.
Top of the range is B200, generating roughly 229 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Where it came from
DeepSeek-R1-Distill-Qwen-14B was published by DeepSeek, in the country recorded as China, during January 2025. 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, Quantitative reasoning, Question answering, Mathematical reasoning, Code generation.
It builds on Qwen2.5-14B. That is the usual way a specialised model is produced.
The weights being open is what puts this page in the calculator rather than only in the catalogue: it is a model you can actually hold. On Hugging Face it is published under the organisation deepseek-ai.
Understanding the speeds
Across every card that can run it, the middle of the range sits at 21.4 tokens per second. Producing text faster than most people read it: 266 of them.
It is a dense model, so every parameter is read for every token produced. That makes speed track memory bandwidth almost exactly — a card with twice the bandwidth generates roughly twice as fast.
Its attention layout is on file, so the memory figures are computed exactly rather than approximated.
What went into building it
It was trained on a corpus of about 24,000,000,000 tokens of text.
Step by step
How to choose a GPU for DeepSeek-R1-Distill-Qwen-14B
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
The table lists every card able to hold DeepSeek-R1-Distill-Qwen-14B, needing around 8.5 GB at a compression of Q3_K_M. That figure, not the headline performance of a card, is what decides whether it runs.
-
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 DeepSeek-R1-Distill-Qwen-14B.
-
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 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
Compare tokens per second, not specifications
Sort by speed to see how cards rank for DeepSeek-R1-Distill-Qwen-14B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 229 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs, but leaves nothing spare for a longer conversation, in the case of DeepSeek-R1-Distill-Qwen-14B. 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 DeepSeek-R1-Distill-Qwen-14B.
Answers
DeepSeek-R1-Distill-Qwen-14B — common questions
DeepSeek-R1-Distill-Qwen-14B— when was it released?
It was published in January 2025.
DeepSeek-R1-Distill-Qwen-14B— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Quantitative reasoning, Question answering, Mathematical reasoning, Code generation. These are the areas it was designed around; they describe intent rather than a hard boundary.
DeepSeek-R1-Distill-Qwen-14B— where can I download it?
Its weights are published on Hugging Face, under the organisation deepseek-ai. We do not host model files — this site calculates what hardware is needed to run them.
DeepSeek-R1-Distill-Qwen-14B— 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 3.0 GB. Every figure here assumes the whole model is resident on the card.
DeepSeek-R1-Distill-Qwen-14B— 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: 306. So a second card is rarely the answer here.
DeepSeek-R1-Distill-Qwen-14B— 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.
DeepSeek-R1-Distill-Qwen-14B— how accurate are these speed estimates?
Every figure is derived from memory bandwidth and model size, not benchmarked, which is why each is published as a range rather than a single number. One example: 195–275 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
DeepSeek-R1-Distill-Qwen-14B— what GPU do I need to run it?
The smallest card in our catalogue that holds it is P102-101, with a memory capacity of 10 GB. It runs the model at a compression of Q3_K_M using about 8.5 GB, and produces roughly 21.0 tokens per second. The number of cards able to run it in total: 306.
DeepSeek-R1-Distill-Qwen-14B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 229 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: 266.
DeepSeek-R1-Distill-Qwen-14B— how much VRAM does it need?
It needs about 8.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.
DeepSeek-R1-Distill-Qwen-14B— 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 Q4_K_M, using about 10.2 GB and generating roughly 60.3 tokens per second. The fit is tight.
DeepSeek-R1-Distill-Qwen-14B— 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 Q6_K, using about 13.7 GB and generating roughly 47.0 tokens per second. The fit is tight.
DeepSeek-R1-Distill-Qwen-14B— 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 17.1 GB and generating roughly 38.4 tokens per second. The fit is comfortable.
DeepSeek-R1-Distill-Qwen-14B— 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.
DeepSeek-R1-Distill-Qwen-14B— how many parameters does it have?
It has a parameter count of 14.8B. 14.8B (safetensors). 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.
DeepSeek-R1-Distill-Qwen-14B— who created it?
It was published by DeepSeek, based in China, an organisation categorised as industry.
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.