Code Llama-70B 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
A100 PCIe 40 GB
40 GB · Q3_K_M · 25.5 tok/s
Fastest card
B200
48.4 tok/s · 180 GB
Which GPUs can run Code Llama-70B?
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.
61 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
48.4
tok/s
41–58 |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 73.8 GB | Q8_0 | Comfortable |
|
48.4
tok/s
41–58 |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 73.8 GB | Q8_0 | Comfortable |
|
38.7
tok/s
23–62 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 73.8 GB | Q8_0 | Comfortable |
|
38.7
tok/s
23–62 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 73.8 GB | Q8_0 | Comfortable |
|
30.9
tok/s
19–49 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 73.8 GB | Q8_0 | Comfortable |
|
29.6
tok/s
25–36 |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 73.8 GB | Q8_0 | Comfortable |
|
29.6
tok/s
25–36 |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 73.8 GB | Q8_0 | Comfortable |
|
29.5
tok/s
25–35 |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 57.5 GB | Q6_K | Comfortable |
|
29.5
tok/s
25–35 |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 57.5 GB | Q6_K | Comfortable |
|
28.3
tok/s
17–45 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 73.8 GB | Q8_0 | Comfortable |
|
26.1
tok/s
22–31 |
GRID A100B NVIDIA | 48 GB | 1,870 GB/s | May 2020 | 41.2 GB | Q4_K_M | Tight |
|
25.5
tok/s
22–31 |
A100 PCIe 40 GB NVIDIA | 40 GB | 1,560 GB/s | Jun 2020 | 33.0 GB | Q3_K_M | Tight |
|
25.5
tok/s
22–31 |
A100 SXM4 40 GB NVIDIA | 40 GB | 1,560 GB/s | May 2020 | 33.0 GB | Q3_K_M | Tight |
|
25.5
tok/s
22–31 |
A800 PCIe 40 GB NVIDIA | 40 GB | 1,560 GB/s | Nov 2022 | 33.0 GB | Q3_K_M | Tight |
|
25.1
tok/s
15–40 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 73.8 GB | Q8_0 | Comfortable |
|
25.1
tok/s
15–40 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 73.8 GB | Q8_0 | Comfortable |
|
25.1
tok/s
15–40 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 73.8 GB | Q8_0 | Comfortable |
|
23.8
tok/s
20–29 |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 73.8 GB | Q8_0 | Tight |
|
20.3
tok/s
17–24 |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 73.8 GB | Q8_0 | Tight |
|
20.3
tok/s
17–24 |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 73.8 GB | Q8_0 | Tight |
|
20.3
tok/s
17–24 |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 73.8 GB | Q8_0 | Tight |
|
18.7
tok/s
16–22 |
RTX PRO 5000 Blackwell NVIDIA | 48 GB | 1,340 GB/s | Mar 2025 | 41.2 GB | Q4_K_M | Tight |
|
17.9
tok/s
15–22 |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 57.5 GB | Q6_K | Comfortable |
|
17.9
tok/s
15–22 |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 57.5 GB | Q6_K | Comfortable |
|
17.9
tok/s
15–22 |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 57.5 GB | Q6_K | 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
- Meta AI
- Organisation type
- Industry
- Country
- United States of America
- Published
- 29 January 2024
- Authors
- Baptiste Rozière, Jonas Gehring, Fabian Gloeckle, Sten Sootla, Itai Gat, Ellen Tan, Yossef (Yossi) Adi, Jingyu Liu, Tal Remez, Jérémy Rapin, Artyom Kozhevnikov, Ivan Evtimov, Joanna Bitton, Manish Bhatt, Cristian Canton Ferrer, Aaron Grattafiori, Wenhan Xiong, Alexandre Defossez, Jade Copet, Faisal Azhar, Hugo Touvron, Gabriel Synnaeve, Louis Martin, Nicolas Usunier, Thomas Scialom
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Code generation
- Base model
- Llama 2-70B
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
- 70B
- Training data
- 3,000,000,000,000 tokens
- Epochs
- 1
- Batch size
- 4,000,000
70B
Llama 70B training dataset was 2 trillion tokens. Code Llama finetuning dataset was 1 trillion tokens of code.
Llama 2 pretraining used 4M batches. I believe the sentence below refers to the training from Llama 2 -> Code Llama-base. "We use a batch size of 4M tokens which are presented as sequences of 4,096 tokens each." Subsequent fine-tuning batch sizes are 500k-1M. "For Code Llama - Instruct, we train with a batch size of 524,288 tokens and on approx. 5B tokens in total... For long context fine-tuning (LCFT)... the batch size is set to 2M tokens for model sizes 7B and 13B and to 1M tokens for mod…
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
- How it was established
- Operation counting
- Fine-tuning compute
- 4.2 × 10²³ FLOP
Base model saw 2T tokens, Code Llama-70B was trained on an additional 1T. 6NC: 6 * 3T * 70B = 1.26e24
Fine tuning from base model uses 1T tokens. 70B * 1T * 6 = 4.2E23
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 A100 SXM4 80 GB
- Chips used
- 400
- Chip-hours
- 2,705,320
- Wall-clock time
- 6,480 hours (270 days)
- Hardware utilisation
- MFU 38.2%
- Power draw
- 316.8 kW
Assuming Code Llama 70B training continued on same hardware as Llama 2 70B. Llama 2 70B used 1720320 A100 hours. Training all Code Llama models took 1.4M A100 hours (Table 26). Based on model sizes and number of tokens seen, 70B model used about 985k A100 hours to fine tune (see utilization notes). Total GPU hours is thus around 2.7M
Based on 6NC estimate, fine tuning required around 4.2e23 FLOP. Table 26 indicates 1400k A100 GPU hours used to train all twelve models, i.e. 1400k * 3600 * 3.12e14 = 1.57e24 FLOP. 70B model trained on 1T tokens while others used 500B. Python finetuning added another 100B tokens to each. 70B's share of total GPU hours was around: (70 billion * 1.1 trillion) / (((7 + 13 + 34) billion * 600 billion) + (70 billion * 1.1 trillion)) = 0.7038 Implies actual GPU-hours for 70B model was: 0.7038 * 1400k …
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
Llama 2 license. can't use outputs to train models. https://github.com/meta-llama/llama/blob/main/LICENSE
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
- Citations
- 3,163
Sources
Where this record came from and when it was last checked.
- Reference
- Code Llama: Open Foundation Models for Code
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run Code Llama-70B
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 48.4 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 48.4 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 38.7 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 38.7 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 30.9 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 29.6 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 29.6 tok/s
- 08 H800 SXM5 80 GB · 3,360 GB/s · Q6_K 29.5 tok/s
- 09 H100 SXM5 80 GB 80 GB · 3,360 GB/s · Q6_K 29.5 tok/s
- 10 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 28.3 tok/s
The smallest GPUs that still run Code Llama-70B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 A800 PCIe 40 GB 40 GB · needs 33.0 GB · Q3_K_M · tight 25.5 tok/s
- 02 A100 PCIe 40 GB 40 GB · needs 33.0 GB · Q3_K_M · tight 25.5 tok/s
- 03 A100 SXM4 40 GB 40 GB · needs 33.0 GB · Q3_K_M · tight 25.5 tok/s
- 04 Radeon PRO W7900D 48 GB · needs 41.2 GB · Q4_K_M · tight 9.4 tok/s
- 05 RTX PRO 5000 Blackwell 48 GB · needs 41.2 GB · Q4_K_M · tight 18.7 tok/s
- 06 RTX 5880 Ada Generation 48 GB · needs 41.2 GB · Q4_K_M · tight 12.1 tok/s
- 07 L20 48 GB · needs 41.2 GB · Q4_K_M · tight 12.1 tok/s
- 08 Radeon PRO W7800 48 GB 48 GB · needs 41.2 GB · Q4_K_M · tight 9.4 tok/s
- 09 Radeon PRO W7900 48 GB · needs 41.2 GB · Q4_K_M · tight 9.4 tok/s
- 10 Data Center GPU Max 1100 48 GB · needs 41.2 GB · Q4_K_M · tight 11.2 tok/s
What the numbers mean
What it takes to run this model
Minimum card
A100 PCIe 40 GB
Memory needed
33.0 GB
Fastest
48.4 tok/s
Code Llama-70B sits at 70B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 61 of the cards we track can hold it.
The smallest card that holds it is the A100 PCIe 40 GB with 40 GB, running it at Q3_K_M and producing around 25.5 tokens per second.
Top of the range is the B200, at roughly 48.4 tokens per second thanks to 8,000 GB/s of bandwidth.
About this model
Code Llama-70B was published by Meta AI, in United States of America, in January 2024. industry is the category the publisher falls under.
It works in Language, and is recorded as doing code generation.
Its starting point was Llama 2-70B — most models at this scale are adapted from an existing base rather than built from nothing.
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.
How fast it runs, and why
Across every card that can run it, the middle of the range is about 17.1 tokens per second, and 49 of them clear the ten tokens per second that roughly matches reading speed.
Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.
Because the architecture is recorded, the memory column is derived rather than estimated.
What went into building it
The training run consumed about 1.3 × 10²⁴ FLOP, on NVIDIA A100 SXM4 80 GB. That figure describes the cost of creating it and has no bearing on how quickly it generates text.
It was trained on about 3,000,000,000,000 tokens of text.
Step by step
How to choose a GPU for Code Llama-70B
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Read the memory figure first
The table lists every card that can hold Code Llama-70B — around 33.0 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Match the context to your actual use
The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context Code Llama-70B can slip off a card that handles short questions easily.
-
03
Set a quality floor
Compression is what makes Code Llama-70B fit smaller cards, at some cost in accuracy — Q3_K_M on the smallest card that fits. A minimum quality removes the ones that go too far.
-
04
Compare tokens per second, not specifications
Ranking by tokens per second for Code Llama-70B follows memory bandwidth, not core counts, which is why the B200 tops it at 48.4 tok/s.
-
05
Check the fit verdict before buying
Tight means Code Llama-70B loads and works, with no room to raise the context later. Comfortable means you can. The difference matters more than a few tokens per second.
-
06
Check the card from the other side
Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for Code Llama-70B alone — a card is usually bought for more than one model.
Answers
Code Llama-70B — common questions
How fast is Code Llama-70B on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 48.4 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 49 of the cards that can run Code Llama-70B clear that.
How much VRAM does Code Llama-70B need?
About 33.0 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.
Is Code Llama-70B open source?
Its weights are published, so Code Llama-70B 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 Code Llama-70B have?
Code Llama-70B has 70B parameters. 70B. 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 Code Llama-70B?
Code Llama-70B was published by Meta AI, based in United States of America, categorised as industry.
When was Code Llama-70B released?
Code Llama-70B 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.
What is Code Llama-70B used for?
Code Llama-70B works in Language, and is recorded as handling code generation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download Code Llama-70B?
The weights for Code Llama-70B are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train Code Llama-70B?
Around 1.3 × 10²⁴ FLOP, on NVIDIA A100 SXM4 80 GB. 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 Code Llama-70B if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down — the nearest miss we calculate is short by 12.4 GB. Our figures for Code Llama-70B assume it is fully resident.
Would two GPUs run Code Llama-70B faster?
Two cards buy memory rather than speed. That matters for Code Llama-70B only if one card cannot hold it — 61 can, so a second adds little.
Why does the quantisation differ between cards for Code Llama-70B?
Because capacity varies, so does how hard Code Llama-70B has to be squeezed — 4 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these Code Llama-70B speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 41–58 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
What GPU do I need to run Code Llama-70B?
The smallest card in our catalogue that holds Code Llama-70B is the A100 PCIe 40 GB, with 40 GB of memory. It runs the model at Q3_K_M using about 33.0 GB, and produces roughly 25.5 tokens per second. 61 cards in total can run it.
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.