MuggleMath 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 MuggleMath?
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
- University of Science and Technology of China (USTC),Alibaba
- Organisation type
- Academia,Industry
- Country
- China
- Published
- 1 November 2023
- Authors
- Chengpeng Li, Zheng Yuan, Hongyi Yuan, Guanting Dong, Keming Lu, Jiancan Wu, Chuanqi Tan, Xiang Wang, Chang Zhou
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language, Mathematics
- Task
- Language modeling/generation, Chat
- 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
- tokens
- Epochs
- 3
model: Apache 2 https://huggingface.co/OFA-Sys/MuggleMath_7B code: undefined license https://github.com/OFA-Sys/gsm8k-ScRel?tab=readme-ov-file#readme
The original GSM8K training set has 7,473 samples. We augment 5 more queries for each query in the training set and yield 7, 473 × 5 = 37, 365 augmented queries.
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
- Chips used
- 32
- Power draw
- 25.4 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 (unrestricted)
- Training code
- Open source
https://huggingface.co/OFA-Sys/MuggleMath_7B
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
- Query and Response Augmentation Cannot Help Out-of-domain Math Reasoning Generalization
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run MuggleMath
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 MuggleMath
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 34.9 GB · Q3_K_M · tight 25.5 tok/s
- 02 A100 PCIe 40 GB 40 GB · needs 34.9 GB · Q3_K_M · tight 25.5 tok/s
- 03 A100 SXM4 40 GB 40 GB · needs 34.9 GB · Q3_K_M · tight 25.5 tok/s
- 04 Radeon PRO W7900D 48 GB · needs 43.0 GB · Q4_K_M · tight 9.4 tok/s
- 05 RTX PRO 5000 Blackwell 48 GB · needs 43.0 GB · Q4_K_M · tight 18.7 tok/s
- 06 RTX 5880 Ada Generation 48 GB · needs 43.0 GB · Q4_K_M · tight 12.1 tok/s
- 07 L20 48 GB · needs 43.0 GB · Q4_K_M · tight 12.1 tok/s
- 08 Radeon PRO W7800 48 GB 48 GB · needs 43.0 GB · Q4_K_M · tight 9.4 tok/s
- 09 Radeon PRO W7900 48 GB · needs 43.0 GB · Q4_K_M · tight 9.4 tok/s
- 10 Data Center GPU Max 1100 48 GB · needs 43.0 GB · Q4_K_M · tight 11.2 tok/s
What the numbers mean
The hardware side
Minimum card
A100 PCIe 40 GB
Memory needed
34.9 GB
Fastest
48.4 tok/s
MuggleMath 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.
At the low end, a A100 PCIe 40 GB handles it — 40 GB, at Q3_K_M, for about 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
MuggleMath was published by University of Science and Technology of China (USTC),Alibaba, in China, in November 2023. It comes out of academia,Industry.
It works in Language, Mathematics, and is recorded as doing language modeling/generation, Chat.
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.
How fast it runs, and why
Half the cards that hold it manage more than 17.1 tokens per second, and 50 exceed reading speed outright.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
Step by step
How to choose a GPU for MuggleMath
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Start from the memory column
The table lists every card that can hold MuggleMath — around 34.9 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.
-
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 MuggleMath stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
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 MuggleMath by squeezing it further than you would want.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for MuggleMath. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 48.4 tok/s.
-
05
Look at the headroom, not just the fit
A tight fit runs MuggleMath but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
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 MuggleMath.
Answers
MuggleMath — common questions
Who created MuggleMath?
MuggleMath was published by University of Science and Technology of China (USTC),Alibaba, based in China, categorised as academia,Industry.
When was MuggleMath released?
MuggleMath 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.
What is MuggleMath used for?
MuggleMath works in Language, Mathematics, and is recorded as handling language modeling/generation, Chat. These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download MuggleMath?
The weights for MuggleMath are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Can I run MuggleMath 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 14.2 GB. Our figures for MuggleMath assume it is fully resident.
Would two GPUs run MuggleMath faster?
A second card roughly doubles the memory available but not the generation rate. With 61 cards already able to run MuggleMath alone, the case for pairing is weak.
Why does the quantisation differ between cards for MuggleMath?
Because capacity varies, so does how hard MuggleMath has to be squeezed — 5 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these MuggleMath speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 29–77 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 MuggleMath?
The smallest card in our catalogue that holds MuggleMath 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.
How fast is MuggleMath 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 MuggleMath clear that.
How much VRAM does MuggleMath 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.
Is MuggleMath open source?
Its weights are published, so MuggleMath 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 MuggleMath have?
MuggleMath has 70B parameters. model: Apache 2 https://huggingface.co/OFA-Sys/MuggleMath_7B code: undefined license https://github.com/OFA-Sys/gsm8k-ScRel?tab=readme-ov-file#readme. 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.
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.