Code Llama-70B TPS calculator

Open weights Meta AI 70B parameters January 2024

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

61 cards that can run it

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

Context length tokens

A longer conversation needs more memory, which can push this model off smaller cards.

Minimum quality

Hides cards that would only fit the model by compressing it below this point.

Search cards

Card memory

Also show cards that cannot run it

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

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

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

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

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.

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.

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 reaches a parameter count of 70B. That puts it above consumer hardware, into the range where a card is bought for this purpose rather than repurposed for it. The number of cards we track that can hold it: 61.

The smallest card that holds it is A100 PCIe 40 GB, with a memory capacity of 40 GB, running it at a compression of Q3_K_M and producing around 25.5 tokens per second.

Top of the range is B200, generating roughly 48.4 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

About this model

Code Llama-70B was published by Meta AI, in the country recorded as United States of America, during January 2024. The category the publisher falls under is industry.

It works in the domain of Language, and is recorded as performing the task of code generation.

Its starting point was an existing base model, 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 sits at 17.1 tokens per second. Producing text faster than most people read it: 49 of them.

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 hardware recorded as NVIDIA A100 SXM4 80 GB. 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 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 able to hold Code Llama-70B, needing around 33.0 GB at a compression of Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
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, because at long context a card that handles short questions easily can be dropped by Code Llama-70B.
03

Set a quality floor

Compression is what makes a model fit smaller cards, at some cost in accuracy, 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

Ranking by tokens per second follows memory bandwidth rather than core counts, for Code Llama-70B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 48.4 tok/s.
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 Code Llama-70B. 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

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. A card is usually bought for more than one model, so it is worth a look before buying for Code Llama-70B.

Answers

Code Llama-70B — common questions

Code Llama-70B— how fast is it on a GPU?

It depends on the card. The quickest we calculate is 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 the number of cards clearing that: 49.

Code Llama-70B— how much VRAM does it need?

It needs about 33.0 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.

Code Llama-70B— 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.

Code Llama-70B— how many parameters does it have?

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

Code Llama-70B— who created it?

It was published by Meta AI, based in United States of America, an organisation categorised as industry.

Code Llama-70B— 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.

Code Llama-70B— what is it used for?

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

Code Llama-70B— where can I download it?

The weights are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

Code Llama-70B— how much compute was used to train it?

Training consumed around 1.3 × 10²⁴ FLOP, on hardware recorded as 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.

Code Llama-70B— 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 12.4 GB. Every figure here assumes the whole model is resident on the card.

Code Llama-70B— 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: 61. So a second card is rarely the answer here.

Code Llama-70B— 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: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

Code Llama-70B— how accurate are these speed estimates?

They are calculated from specifications rather than measured, and each carries a range. One example: 41–58 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

Code Llama-70B— what GPU do I need to run it?

The smallest card in our catalogue that holds it is A100 PCIe 40 GB, with a memory capacity of 40 GB. It runs the model at a compression of Q3_K_M using about 33.0 GB, and produces roughly 25.5 tokens per second. The number of cards able to run it in total: 61.

Source

Original publication

Record last updated 25 May 2026

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.

All AI models