MPT-30B 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
RTX A4500
20 GB · IQ4_XS · 22.2 tok/s
Fastest card
B200
113 tok/s · 180 GB
Which GPUs can run MPT-30B?
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.
132 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
113
tok/s
68–181 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 32.8 GB | Q8_0 | Comfortable |
|
113
tok/s
68–181 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 32.8 GB | Q8_0 | Comfortable |
|
90.2
tok/s
54–144 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 32.8 GB | Q8_0 | Comfortable |
|
90.2
tok/s
54–144 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 32.8 GB | Q8_0 | Comfortable |
|
72.1
tok/s
43–115 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 32.8 GB | Q8_0 | Comfortable |
|
69.0
tok/s
41–110 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 32.8 GB | Q8_0 | Comfortable |
|
69.0
tok/s
41–110 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 32.8 GB | Q8_0 | Comfortable |
|
66.1
tok/s
40–106 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 32.8 GB | Q8_0 | Comfortable |
|
58.6
tok/s
35–94 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 32.8 GB | Q8_0 | Comfortable |
|
58.6
tok/s
35–94 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 32.8 GB | Q8_0 | Comfortable |
|
58.6
tok/s
35–94 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 32.8 GB | Q8_0 | Comfortable |
|
55.6
tok/s
33–89 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 32.8 GB | Q8_0 | Comfortable |
|
47.4
tok/s
28–76 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 32.8 GB | Q8_0 | Comfortable |
|
47.4
tok/s
28–76 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 32.8 GB | Q8_0 | Comfortable |
|
47.4
tok/s
28–76 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 32.8 GB | Q8_0 | Comfortable |
|
47.4
tok/s
28–76 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 32.8 GB | Q8_0 | Comfortable |
|
47.4
tok/s
28–76 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 32.8 GB | Q8_0 | Comfortable |
|
43.7
tok/s
26–70 · low confidence |
GeForce RTX 5090 D V2 NVIDIA | 24 GB | 1,340 GB/s | Aug 2025 | 18.8 GB | Q4_K_M | Tight |
|
39.8
tok/s
24–64 · low confidence |
A30X NVIDIA | 24 GB | 1,220 GB/s | Apr 2021 | 18.8 GB | Q4_K_M | Tight |
|
38.4
tok/s
23–61 · low confidence |
DRIVE A100 PROD NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 25.8 GB | Q6_K | Tight |
|
38.4
tok/s
23–61 · low confidence |
GRID A100A NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 25.8 GB | Q6_K | Tight |
|
36.7
tok/s
22–59 · low confidence |
GeForce RTX 5090 NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 25.8 GB | Q6_K | Tight |
|
36.7
tok/s
22–59 · low confidence |
GeForce RTX 5090 D NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 25.8 GB | Q6_K | Tight |
|
36.1
tok/s
22–58 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 32.8 GB | Q8_0 | Comfortable |
|
36.1
tok/s
22–58 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 32.8 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
- MosaicML
- Organisation type
- Industry
- Country
- United States of America
- Published
- 22 June 2023
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language generation, 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
- 30B
- Training data
- 1,050,000,000,000 tokens
- Epochs
- 1
- Batch size
- 4,096,000
30B
~4T tokens across sources, but only trained on 1.05T of these
last two batch sizes were 3,456,000 and 4,096,000, but 4,096,000 only used for last 5% of training "To build 8k support into MPT-30B efficiently, we first pre-trained on 1T tokens using sequences that were 2k tokens long, and then trained for an additional 50B tokens using sequences that were 8k tokens long... The model was trained in three stages using the MosaicML Platform: (i) First it was trained on 440 A100-40GBs with a batch size of 1760. (ii) Then, on 216 A100-40GBs with a batch size of…
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.9 × 10²³ FLOP
- How it was established
- Operation counting
According to their blog post, "MPT-30B FLOPs ~= 6 * 30e9 [params] * 1.05e12 [tokens] = 1.89e23 FLOPs"
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 H100 SXM5 80GB
- Chips used
- 512
- Chip-hours
- 142,541
- Wall-clock time
- 278 hours (11.6 days)
- Power draw
- 713.2 kW
- Cloud vendor
- Databricks
30B: 512x H100-80gb for 11.6 days
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 (unrestricted)
- Training code
- Open source
- Hugging Face
- mosaicml
apache 2.0 for weights. pretrain code here: https://github.com/mosaicml/llm-foundry/tree/main/scripts/train/yamls/pretrain
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
Sources
Where this record came from and when it was last checked.
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run MPT-30B
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 113 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 113 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 90.2 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 90.2 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 72.1 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 69.0 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 69.0 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 66.1 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 58.6 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 58.6 tok/s
The smallest GPUs that still run MPT-30B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 RTX 4000 Ada Generation 20 GB · needs 17.1 GB · IQ4_XS · tight 12.5 tok/s
- 02 RTX 4000 SFF Ada Generation 20 GB · needs 17.1 GB · IQ4_XS · tight 9.7 tok/s
- 03 Radeon RX 7900 XT 20 GB · needs 17.1 GB · IQ4_XS · tight 21.6 tok/s
- 04 A10M 20 GB · needs 17.1 GB · IQ4_XS · tight 17.3 tok/s
- 05 GeForce RTX 3080 Ti 20 GB 20 GB · needs 17.1 GB · IQ4_XS · tight 26.4 tok/s
- 06 RTX A4500 20 GB · needs 17.1 GB · IQ4_XS · tight 22.2 tok/s
- 07 Arc Pro B60 24 GB · needs 18.8 GB · Q4_K_M · tight 9.7 tok/s
- 08 GeForce RTX 5090 D V2 24 GB · needs 18.8 GB · Q4_K_M · tight 43.7 tok/s
- 09 RTX PRO 4000 Blackwell SFF 24 GB · needs 18.8 GB · Q4_K_M · tight 14.1 tok/s
- 10 GeForce RTX 5090 Mobile 24 GB · needs 18.8 GB · Q4_K_M · tight 29.2 tok/s
What the numbers mean
What you need to run it
Minimum card
RTX A4500
Memory needed
17.1 GB
Fastest
113 tok/s
MPT-30B reaches a parameter count of 30B. That lands in the range a serious desktop card can handle once the weights are compressed. The number of cards we track that can run it: 132.
The least hardware that works is RTX A4500, with a memory capacity of 20 GB, running it at a compression of IQ4_XS and producing around 22.2 tokens per second.
Top of the range is B200, generating roughly 113 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
What this model is
MPT-30B was published by MosaicML, in the country recorded as United States of America, during June 2023. It comes out of an organisation categorised as industry.
It works in the domain of Language, and is recorded as performing the task of language generation, Code generation.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. On Hugging Face it is published under the organisation mosaicml.
What decides the speed
Across every card that can run it, the middle of the range sits at 22.0 tokens per second. Exceeding reading speed outright: 104 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.
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.
Training and provenance
The training run consumed about 1.9 × 10²³ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. 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 1,050,000,000,000 tokens of text.
Step by step
How to choose a GPU for MPT-30B
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
Start from what it actually needs, which is the requirement of MPT-30B, needing around 17.1 GB at a compression of IQ4_XS. No amount of processing power compensates for a card that cannot hold it.
-
02
Set the context length you will work at
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for MPT-30B.
-
03
Decide how much compression you will accept
The quantisation column varies by card, because a bigger card holds a more accurate copy, reaching a compression of IQ4_XS 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
Sort by speed
Sort by speed to see how cards rank for MPT-30B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 113 tok/s.
-
05
Read the fit column last
A tight fit runs, but leaves nothing spare for a longer conversation, in the case of MPT-30B. 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 MPT-30B.
Answers
MPT-30B — common questions
MPT-30B— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 68–181 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
MPT-30B— what GPU do I need to run it?
The smallest card in our catalogue that holds it is RTX A4500, with a memory capacity of 20 GB. It runs the model at a compression of IQ4_XS using about 17.1 GB, and produces roughly 22.2 tokens per second. The number of cards able to run it in total: 132.
MPT-30B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 113 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: 104.
MPT-30B— how much VRAM does it need?
It needs about 17.1 GB at a compression of IQ4_XS, 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.
MPT-30B— 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 Q4_K_M, using about 18.8 GB and generating roughly 43.7 tokens per second. The fit is tight.
MPT-30B— 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.
MPT-30B— how many parameters does it have?
It has a parameter count of 30B. 30B. 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.
MPT-30B— who created it?
It was published by MosaicML, based in United States of America, an organisation categorised as industry.
MPT-30B— when was it released?
It was published in June 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.
MPT-30B— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language generation, Code generation. These are the areas it was designed around; they describe intent rather than a hard boundary.
MPT-30B— where can I download it?
Its weights are published on Hugging Face, under the organisation mosaicml. We do not host model files — this site calculates what hardware is needed to run them.
MPT-30B— how much compute was used to train it?
Training consumed around 1.9 × 10²³ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. 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.
MPT-30B— can I run it if it does not fit in my GPU?
Partly. Layers that do not fit sit in system memory and run at a fraction of the speed, so a mostly-offloaded model is rarely worth using. The nearest miss we calculate falls short by 4.4 GB. Every figure here assumes the whole model is resident on the card.
MPT-30B— would two GPUs run it faster?
Capacity adds across cards; throughput does not. The number of cards already holding it on their own: 132. So a second card is rarely the answer here.
MPT-30B— 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: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
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.