Llama 3.1-70B TPS calculator

Open weights Meta AI 70B parameters July 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 Llama 3.1-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
23 July 2024
Authors
Abhimanyu Dubey, Abhinav Jauhri, Abhinav Pandey, Abhishek Kadian, Ahmad Al-Dahle, Aiesha Letman, Alan Schelten, Amy Yang, Angela Fan, Anirudh Goyal, Anthony Hartshorn, Aobo Yang, Archi Mitra, Archie Sravankumar, Artem Korenev, Arthur Hinsvark, Arun Rao, Aston Zhang, Aurelien Rodriguez, Austen Gregerson, Ava Spataru, Baptiste Roziere, Bethany Biron, Binh Tang, Bobbie Chern, Charlotte Caucheteux, Ch…

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Language
Task
Language modeling/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
70B

70B

Training data
15,000,000,000,000 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
7.9 × 10²⁴ FLOP

Huggingface page says 3.1-70B used 7.0M H100 hours and trained over 15T tokens. https://huggingface.co/meta-llama/Llama-3.1-70B The paper also says that 3.1-405B got MFU of between 38-43%; presumably 70B was around the same or a bit higher. I'll assume utilization of 40% 6ND: 6 * 15T * 70B = 6.3e24 FLOPs Hardware: 7M * 9.9e14 * 3600 * 0.4 = 9.98e24 FLOPs Geometric mean: sqrt(6.3e24 * 9.98e24) = 7.929e24 Note that Llama 3-70B also said it used 15T tokens, but only 6.4M H100 hours. This sugges…

How it was established
Hardware,Operation counting

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
Open (restricted use)

Llama 3.1 license: https://huggingface.co/meta-llama/Meta-Llama-3.1-8B/blob/main/LICENSE must seek separate license if over 700m monthly users, acceptable use restrictions code here: https://github.com/meta-llama/llama3/tree/main

Hugging Face
meta-llama

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
The Llama 3 Herd of Models
Last updated
28 November 2025

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

A100 PCIe 40 GB

Memory needed

33.0 GB

Fastest

48.4 tok/s

Llama 3.1-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 entry point is the A100 PCIe 40 GB: 40 GB of memory, Q3_K_M compression, roughly 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.

Background

Llama 3.1-70B was published by Meta AI, in United States of America, in July 2024. industry is the category the publisher falls under.

It works in Language, and is recorded as doing language modeling/generation.

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. It is published under the meta-llama organisation on Hugging Face.

Reading the throughput figures

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.

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.

Training and provenance

Training it took roughly 7.9 × 10²⁴ FLOP of computation — a measure of what producing the model cost, not of how fast it answers.

The training set ran to roughly 15,000,000,000,000 tokens.

The reason it appears in this catalogue at all is training cost.

Step by step

How to choose a GPU for Llama 3.1-70B

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Start from the memory column

    Look at what Llama 3.1-70B actually needs — around 33.0 GB at Q3_K_M. No amount of processing power compensates for a card that cannot hold it.

  2. 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 Llama 3.1-70B can slip off a card that handles short questions easily.

  3. 03

    Set a quality floor

    Each card runs the least-compressed copy it can hold — Q3_K_M on the smallest card that fits. Setting a floor drops the cards that only manage Llama 3.1-70B by squeezing it further than you would want.

  4. 04

    Compare tokens per second, not specifications

    The speed ordering for Llama 3.1-70B is effectively an ordering by memory bandwidth, which is why the B200 tops it at 48.4 tok/s.

  5. 05

    Check the fit verdict before buying

    Tight means Llama 3.1-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.

  6. 06

    Open the card you have settled on

    Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond Llama 3.1-70B.

Answers

Llama 3.1-70B — common questions

01

Would two GPUs run Llama 3.1-70B faster?

Two cards buy memory rather than speed. That matters for Llama 3.1-70B only if one card cannot hold it — 61 can, so a second adds little.

02

Why does the quantisation differ between cards for Llama 3.1-70B?

A larger card holds a more accurate copy. Across the cards that run Llama 3.1-70B, 4 compression levels are used; the floor control above pins it to one.

03

How accurate are these Llama 3.1-70B speed estimates?

These are estimates with real error bars. The fastest result here, 41–58 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.

04

What GPU do I need to run Llama 3.1-70B?

The smallest card in our catalogue that holds Llama 3.1-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.

05

How fast is Llama 3.1-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 Llama 3.1-70B clear that.

06

How much VRAM does Llama 3.1-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.

07

Is Llama 3.1-70B open source?

Its weights are published, so Llama 3.1-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.

08

How many parameters does Llama 3.1-70B have?

Llama 3.1-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.

09

Who created Llama 3.1-70B?

Llama 3.1-70B was published by Meta AI, based in United States of America, categorised as industry.

10

When was Llama 3.1-70B released?

Llama 3.1-70B was published in July 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.

11

What is Llama 3.1-70B used for?

Llama 3.1-70B works in Language, and is recorded as handling language modeling/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.

12

Where can I download Llama 3.1-70B?

Its weights are published under the meta-llama organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.

13

How much compute was used to train Llama 3.1-70B?

Around 7.9 × 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.

14

Can I run Llama 3.1-70B if it does not fit in my GPU?

It can be split between the card and system memory, but Llama 3.1-70B generates painfully slowly that way — the nearest miss we calculate is short by 12.4 GB. Nothing on this page assumes offloading.

Source

Original publication

Record last updated 28 November 2025

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.