Meditron-70B TPS calculator

Open weights Ecole Polytechnique F´ed´erale de Lausanne (EPFL) 70B parameters November 2023

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 Meditron-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

29–77 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 75.6 GB Q8_0 Comfortable
48.4 tok/s

29–77 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 75.6 GB Q8_0 Comfortable
38.7 tok/s

23–62 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 75.6 GB Q8_0 Comfortable
38.7 tok/s

23–62 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 75.6 GB Q8_0 Comfortable
30.9 tok/s

19–49 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 75.6 GB Q8_0 Comfortable
29.6 tok/s

18–47 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 75.6 GB Q8_0 Comfortable
29.6 tok/s

18–47 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 75.6 GB Q8_0 Comfortable
29.5 tok/s

18–47 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 59.3 GB Q6_K Comfortable
29.5 tok/s

18–47 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 59.3 GB Q6_K Comfortable
28.3 tok/s

17–45 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 75.6 GB Q8_0 Comfortable
26.1 tok/s

16–42 · low confidence

GRID A100B NVIDIA 48 GB 1,870 GB/s May 2020 43.0 GB Q4_K_M Tight
25.5 tok/s

15–41 · low confidence

A100 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Jun 2020 34.9 GB Q3_K_M Tight
25.5 tok/s

15–41 · low confidence

A100 SXM4 40 GB NVIDIA 40 GB 1,560 GB/s May 2020 34.9 GB Q3_K_M Tight
25.5 tok/s

15–41 · low confidence

A800 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Nov 2022 34.9 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 75.6 GB Q8_0 Comfortable
25.1 tok/s

15–40 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 75.6 GB Q8_0 Comfortable
25.1 tok/s

15–40 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 75.6 GB Q8_0 Comfortable
23.8 tok/s

14–38 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 75.6 GB Q8_0 Tight
21.8 tok/s

13–35 · low confidence

H100 SXM5 64 GB NVIDIA 64 GB 2,020 GB/s Mar 2023 51.2 GB Q5_K_M Tight
20.3 tok/s

12–33 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 75.6 GB Q8_0 Tight
20.3 tok/s

12–33 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 75.6 GB Q8_0 Tight
20.3 tok/s

12–33 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 75.6 GB Q8_0 Tight
18.7 tok/s

11–30 · low confidence

RTX PRO 5000 Blackwell NVIDIA 48 GB 1,340 GB/s Mar 2025 43.0 GB Q4_K_M Tight
17.9 tok/s

11–29 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 59.3 GB Q6_K Comfortable
17.9 tok/s

11–29 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 59.3 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
Ecole Polytechnique F´ed´erale de Lausanne (EPFL)
Organisation type
Academia
Country
Switzerland
Published
27 November 2023
Authors
Zeming Chen, Alejandro Hernández Cano, Angelika Romanou, Antoine Bonnet, Kyle Matoba, Francesco Salvi, Matteo Pagliardini, Simin Fan, Andreas Köpf, Amirkeivan Mohtashami, Alexandre Sallinen, Alireza Sakhaeirad, Vinitra Swamy, Igor Krawczuk, Deniz Bayazit, Axel Marmet, Syrielle Montariol, Mary-Anne Hartley, Martin Jaggi, Antoine Bosselut

What it does

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

Domain
Language, Medicine
Task
Language modeling/generation, Question answering, Medical diagnosis
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

70B

Training data
48,100,000,000 tokens

"MEDITRON ’s domain-adaptive pre-training corpus GAP-REPLAY combines 48.1B tokens from four datasets"

Epochs
1

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
Hardware,Operation counting
Fine-tuning compute
3.1 × 10²² FLOP

"For the pretraining run with Llama-2-70B, we achieve a throughput of 40, 200 tokens/second. This amounts to 1.6884 × 10^16 bfloat16 flop/second and represents roughly 42.3% of the theoretical peak flops of 128 A100 GPUs, which is 128 × (312 × 1012) = 3.9936 × 10^16 flops. " 3.9936 × 10^16 FLOP / sec * 332 hours [see training time notes] * 3600 sec / hour = 4.7731507e+22 FLOP 6 FLOP / parameter / token * 70 * 10^9 parameters * 48.1 * 10^9 tokens = 2.0202e+22 FLOP sqrt(4.7731507e+22*2.0202e+22…

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
128
Wall-clock time
332 hours (13.8 days)

"For the pretraining run with Llama-2-70B, we achieve a throughput of 40, 200 tokens/second. This amounts to 1.6884 × 10^16 bfloat16 flop/second and represents roughly 42.3% of the theoretical peak flops of 128 A100 GPUs, which is 128 × (312 × 1012) = 3.9936 × 10^16 flops. " "Our training of the 70B model ran for 332 hours on 128 A100 GPUs, for 42,496 GPU-hours."

Hardware utilisation
HFU 42.3%

"For the pretraining run with Llama-2-70B, we achieve a throughput of 40, 200 tokens/second. This amounts to 1.6884 × 1016 bfloat16 flop/second and represents roughly 42.3% of the theoretical peak flops of 128 A100 GPUs, which is 128 × (312 × 1012) = 3.9936 × 1016 flops." HFU = 1.6884*10^16 FLOPS / (128 * 311.84*10^12 FLOPS) = 0.42299

Power draw
101.5 kW
Data centre
Hardware Provider: EPFL Research Computing Platform, Compute Region: Switzerland

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 https://huggingface.co/epfl-llm/meditron-70b

Hugging Face
epfl-llm

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Record confidence
Confident

Sources

Where this record came from and when it was last checked.

Reference
MEDITRON-70B: Scaling Medical Pretraining for Large Language Models
Last updated
28 November 2025

The extremes

What the numbers mean

What you need to run it

Minimum card

A100 PCIe 40 GB

Memory needed

34.9 GB

Fastest

48.4 tok/s

Meditron-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 least hardware that works is a A100 PCIe 40 GB. Its 40 GB is enough at Q3_K_M compression, giving roughly 25.5 tokens per second.

The quickest result comes from a B200 at around 48.4 tokens per second — its 8,000 GB/s of bandwidth is what buys that.

Background

Meditron-70B was published by Ecole Polytechnique F´ed´erale de Lausanne (EPFL), in Switzerland, in November 2023. It comes out of academia.

It works in Language, Medicine, and is recorded as doing language modeling/generation, Question answering, Medical diagnosis.

It is derived from Llama 2-70B rather than trained from scratch, which is the usual way a specialised model is produced.

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. It is published under the epfl-llm 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 50 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.

Without the attention layout on record, the memory column is an approximation. It is close enough to choose hardware by, and least reliable at long context.

How it was trained

Around 48,100,000,000 tokens went into training it.

Step by step

How to choose a GPU for Meditron-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

    Check what it needs before anything else

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

  2. 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 Meditron-70B stops fitting a card that seemed fine.

  3. 03

    Choose how far you will compress it

    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 Meditron-70B by squeezing it further than you would want.

  4. 04

    Compare tokens per second, not specifications

    Ranking by tokens per second for Meditron-70B follows memory bandwidth, not core counts, which is why the B200 tops it at 48.4 tok/s.

  5. 05

    Look at the headroom, not just the fit

    A tight fit runs Meditron-70B but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.

  6. 06

    Open the card you have settled on

    Following a card through to its own page shows every other model it can hold, which is the question that follows once Meditron-70B is settled.

Answers

Meditron-70B — common questions

01

Would two GPUs run Meditron-70B faster?

A second card roughly doubles the memory available but not the generation rate. With 61 cards already able to run Meditron-70B alone, the case for pairing is weak.

02

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

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

03

How accurate are these Meditron-70B speed estimates?

Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 29–77 tok/s on the B200 rather than a single number.

04

What GPU do I need to run Meditron-70B?

The smallest card in our catalogue that holds Meditron-70B is the A100 PCIe 40 GB, with 40 GB of memory. It runs the model at Q3_K_M using about 34.9 GB, and produces roughly 25.5 tokens per second. 61 cards in total can run it.

05

How fast is Meditron-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 50 of the cards that can run Meditron-70B clear that.

06

How much VRAM does Meditron-70B need?

About 34.9 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 Meditron-70B open source?

Its weights are published, so Meditron-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 Meditron-70B have?

Meditron-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 Meditron-70B?

Meditron-70B was published by Ecole Polytechnique F´ed´erale de Lausanne (EPFL), based in Switzerland, categorised as academia.

10

When was Meditron-70B released?

Meditron-70B was published in November 2023. 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 Meditron-70B used for?

Meditron-70B works in Language, Medicine, and is recorded as handling language modeling/generation, Question answering, Medical diagnosis. These are the areas it was designed around; they describe intent rather than a hard boundary.

12

Where can I download Meditron-70B?

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

13

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

It can be split between the card and system memory, but Meditron-70B generates painfully slowly that way — the nearest miss we calculate is short by 14.2 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.