DeepSeek Coder 1.3B 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
Tesla C1080
4 GB · Q8_0 · 28.4 tok/s
Fastest card
B200
2,606 tok/s · 180 GB
Which GPUs can run DeepSeek Coder 1.3B?
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.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
2,606
tok/s
1,564–4,170 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 2.1 GB | Q8_0 | Comfortable |
|
2,606
tok/s
1,564–4,170 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 2.1 GB | Q8_0 | Comfortable |
|
2,081
tok/s
1,249–3,330 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 2.1 GB | Q8_0 | Comfortable |
|
2,081
tok/s
1,249–3,330 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 2.1 GB | Q8_0 | Comfortable |
|
1,664
tok/s
999–2,663 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,593
tok/s
956–2,549 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 2.1 GB | Q8_0 | Comfortable |
|
1,593
tok/s
956–2,549 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 2.1 GB | Q8_0 | Comfortable |
|
1,525
tok/s
915–2,440 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 2.1 GB | Q8_0 | Comfortable |
|
1,353
tok/s
812–2,165 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,353
tok/s
812–2,165 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,353
tok/s
812–2,165 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,284
tok/s
770–2,054 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
1,095
tok/s
657–1,751 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 2.1 GB | Q8_0 | Comfortable |
|
834
tok/s
500–1,334 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 2.1 GB | Q8_0 | Comfortable |
|
834
tok/s
500–1,334 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 2.1 GB | Q8_0 | Comfortable |
|
695
tok/s
417–1,111 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 2.1 GB | Q8_0 | Comfortable |
|
680
tok/s
408–1,088 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 2.1 GB | Q8_0 | Comfortable |
|
665
tok/s
399–1,063 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 2.1 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
- DeepSeek,Peking University
- Organisation type
- Industry,Academia
- Country
- China
- Published
- 25 January 2024
- Authors
- Daya Guo, Qihao Zhu, Dejian Yang, Zhenda Xie, Kai Dong, Wentao Zhang, Guanting Chen, Xiao Bi, Y. Wu, Y.K. Li, Fuli Luo, Yingfei Xiong, Wenfeng Liang
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- 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
- 1.3B
- Training data
- 2,000,000,000,000 tokens
1.3B
"Trained from scratch on 2T tokens, including 87% code and 13% linguistic data in both English and Chinese languages." "The total data volume is 798 GB with 603 million files."
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.6 × 10²² FLOP
- How it was established
- Operation counting
2T tokens * 1.3B parameters * 6 FLOP / parameter / token = 15.6 * 10^21 = 1.56 * 10^22 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 (restricted use)
- Training code
- Unreleased
- Hugging Face
- deepseek-ai
code doesn't seem to be training code. deepseek license: https://github.com/deepseek-ai/DeepSeek-Coder/blob/main/LICENSE-MODEL
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- DeepSeek-Coder: When the Large Language Model Meets Programming -- The Rise of Code Intelligence
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run DeepSeek Coder 1.3B
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 2,606 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 2,606 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 2,081 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 2,081 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 1,664 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 1,593 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 1,593 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 1,525 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 1,353 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 1,353 tok/s
The smallest GPUs that still run DeepSeek Coder 1.3B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 2.1 GB · Q8_0 · comfortable 31.3 tok/s
- 02 RTX A400 4 GB · needs 2.1 GB · Q8_0 · comfortable 31.3 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 2.1 GB · Q8_0 · comfortable 41.7 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 2.1 GB · Q8_0 · comfortable 62.6 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 2.1 GB · Q8_0 · comfortable 11.1 tok/s
- 06 Radeon RX 6450M 4 GB · needs 2.1 GB · Q8_0 · comfortable 32.5 tok/s
- 07 Radeon RX 6550M 4 GB · needs 2.1 GB · Q8_0 · comfortable 36.6 tok/s
- 08 Radeon RX 6550S 4 GB · needs 2.1 GB · Q8_0 · comfortable 32.5 tok/s
- 09 Arc A310 4 GB · needs 2.1 GB · Q8_0 · comfortable 26.3 tok/s
- 10 Arc Pro A30M 4 GB · needs 2.1 GB · Q8_0 · comfortable 27.1 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
2.1 GB
Fastest
2,606 tok/s
DeepSeek Coder 1.3B reaches a parameter count of 1.3B. 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: 818.
The entry point is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 28.4 tokens per second.
The quickest result comes from B200, generating roughly 2,606 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
What this model is
DeepSeek Coder 1.3B was published by DeepSeek,Peking University, in the country recorded as China, during January 2024. It comes out of an organisation categorised as industry,Academia.
It works in the domain of Language, and is recorded as performing the task of code generation.
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.
What decides the speed
The median result is around 73.2 tokens per second. Producing text faster than most people read it: 797 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
Training it took a computation budget of roughly 1.6 × 10²² FLOP. 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 2,000,000,000,000 tokens of text.
Step by step
How to choose a GPU for DeepSeek Coder 1.3B
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 DeepSeek Coder 1.3B, needing around 2.1 GB at a compression of Q8_0. No amount of processing power compensates for a card that cannot hold it.
-
02
Decide how long your conversations run
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for DeepSeek Coder 1.3B.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold, reaching a compression of Q8_0 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
Sort by speed to see how cards rank for DeepSeek Coder 1.3B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 2,606 tok/s.
-
05
Look at the headroom, not just the fit
Tight means it loads and works with no room to raise the context later, in the case of DeepSeek Coder 1.3B. 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 Coder 1.3B.
Answers
DeepSeek Coder 1.3B — common questions
DeepSeek Coder 1.3B— how much compute was used to train it?
Training consumed around 1.6 × 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.
DeepSeek Coder 1.3B— 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. Every figure here assumes the whole model is resident on the card.
DeepSeek Coder 1.3B— would two GPUs run it faster?
A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 818. So a second card is rarely the answer here.
DeepSeek Coder 1.3B— why does the quantisation differ between cards?
Because capacity varies, so does how hard it has to be squeezed. The number of distinct levels in the table above: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
DeepSeek Coder 1.3B— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 1,564–4,170 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 Coder 1.3B— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Tesla C1080, with a memory capacity of 4 GB. It runs the model at a compression of Q8_0 using about 2.1 GB, and produces roughly 28.4 tokens per second. The number of cards able to run it in total: 818.
DeepSeek Coder 1.3B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 2,606 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: 797.
DeepSeek Coder 1.3B— how much VRAM does it need?
It needs about 2.1 GB at a compression of Q8_0, 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 Coder 1.3B— can I run it on a GPU holding 8 GB?
Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of Q8_0, using about 2.1 GB and generating roughly 485 tokens per second. The fit is comfortable.
DeepSeek Coder 1.3B— 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 Q8_0, using about 2.1 GB and generating roughly 297 tokens per second. The fit is comfortable.
DeepSeek Coder 1.3B— 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 Q8_0, using about 2.1 GB and generating roughly 368 tokens per second. The fit is comfortable.
DeepSeek Coder 1.3B— 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 2.1 GB and generating roughly 437 tokens per second. The fit is comfortable.
DeepSeek Coder 1.3B— 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 Coder 1.3B— how many parameters does it have?
It has a parameter count of 1.3B. 1.3B. 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 Coder 1.3B— who created it?
It was published by DeepSeek,Peking University, based in China, an organisation categorised as industry,Academia.
DeepSeek Coder 1.3B— when was it released?
It was published in January 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.
DeepSeek Coder 1.3B— what is it used for?
It works in the domain of Language, and is recorded as handling the task of code generation. 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.
DeepSeek Coder 1.3B— 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.
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.