MatterGen 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
Tesla C1080
4 GB · Q8_0 · 788 tok/s
Fastest card
B200
72,398 tok/s · 180 GB
Which GPUs can run MatterGen?
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.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
72,398
tok/s
43,439–115,837 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 0.7 GB | Q8_0 | Comfortable |
|
72,398
tok/s
43,439–115,837 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 0.7 GB | Q8_0 | Comfortable |
|
57,812
tok/s
34,687–92,499 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.7 GB | Q8_0 | Comfortable |
|
57,812
tok/s
34,687–92,499 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.7 GB | Q8_0 | Comfortable |
|
46,235
tok/s
27,741–73,976 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 0.7 GB | Q8_0 | Comfortable |
|
44,253
tok/s
26,552–70,805 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.7 GB | Q8_0 | Comfortable |
|
44,253
tok/s
26,552–70,805 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.7 GB | Q8_0 | Comfortable |
|
42,353
tok/s
25,412–67,765 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 0.7 GB | Q8_0 | Comfortable |
|
37,588
tok/s
22,553–60,141 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 0.7 GB | Q8_0 | Comfortable |
|
37,588
tok/s
22,553–60,141 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.7 GB | Q8_0 | Comfortable |
|
37,588
tok/s
22,553–60,141 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.7 GB | Q8_0 | Comfortable |
|
35,656
tok/s
21,394–57,050 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
30,407
tok/s
18,244–48,652 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
30,407
tok/s
18,244–48,652 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 0.7 GB | Q8_0 | Comfortable |
|
30,407
tok/s
18,244–48,652 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
30,407
tok/s
18,244–48,652 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
30,407
tok/s
18,244–48,652 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
23,153
tok/s
13,892–37,045 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.7 GB | Q8_0 | Comfortable |
|
23,153
tok/s
13,892–37,045 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.7 GB | Q8_0 | Comfortable |
|
19,294
tok/s
11,576–30,871 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 0.7 GB | Q8_0 | Comfortable |
|
18,882
tok/s
11,329–30,212 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 0.7 GB | Q8_0 | Comfortable |
|
18,462
tok/s
11,077–29,538 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 0.7 GB | Q8_0 | Comfortable |
|
18,462
tok/s
11,077–29,538 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 0.7 GB | Q8_0 | Comfortable |
|
18,462
tok/s
11,077–29,538 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 0.7 GB | Q8_0 | Comfortable |
|
18,462
tok/s
11,077–29,538 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 0.7 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
- Microsoft Research AI for Science
- Organisation type
- Industry
- Country
- United States of America
- Published
- 16 January 2025
- Authors
- Claudio Zeni, Robert Pinsler, Daniel Zügner, Andrew Fowler, Matthew Horton, Xiang Fu, Zilong Wang, Aliaksandra Shysheya, Jonathan Crabbé, Shoko Ueda, Roberto Sordillo, Lixin Sun, Jake Smith, Bichlien Nguyen, Hannes Schulz, Sarah Lewis, Chin-Wei Huang, Ziheng Lu, Yichi Zhou, Han Yang, Hongxia Hao, Jielan Li, Chunlei Yang, Wenjie Li, Ryota Tomioka, Tian Xie
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Materials science
- Task
- Materials design, Crystal discovery
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
- 46.8M
- Training data
- tokens
- Epochs
- 100
"MatterGen contains 46.8M parameters" https://huggingface.co/microsoft/mattergen "The model architecture is based on GemNet (Gasteiger et al. 2021)."
"It is trained on 608,000 stable materials from the Materials Project(opens in new tab) (MP) and Alexandria(opens in new tab) (Alex) databases." 26956800000000000000 (estimated training compute) / (46800000 parameters * 6 * 100 epochs * 608000 materials) ~ 1579 tokens per materials 1579*608,000 = 960032000
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
- 2.7 × 10¹⁹ FLOP
- How it was established
- Hardware
312000000000000*3600*10*8*0.3 = 2.69568e+19
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
- 8
- Wall-clock time
- 10 hours
- Power draw
- 6.3 kW
"One training epoch of around 600K training samples takes around 6 minutes on 8 NVIDIA A100 GPUs" 100 epochs -> 600 minutes = 10 hours
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
- microsoft
MIT license https://huggingface.co/microsoft/mattergen https://github.com/microsoft/mattergen
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
- A generative model for inorganic materials design
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run MatterGen
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 72,398 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 72,398 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 57,812 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 57,812 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 46,235 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 44,253 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 44,253 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 42,353 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 37,588 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 37,588 tok/s
The smallest GPUs that still run MatterGen
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 0.7 GB · Q8_0 · comfortable 869 tok/s
- 02 RTX A400 4 GB · needs 0.7 GB · Q8_0 · comfortable 869 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,158 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,738 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 0.7 GB · Q8_0 · comfortable 309 tok/s
- 06 Radeon RX 6450M 4 GB · needs 0.7 GB · Q8_0 · comfortable 904 tok/s
- 07 Radeon RX 6550M 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,016 tok/s
- 08 Radeon RX 6550S 4 GB · needs 0.7 GB · Q8_0 · comfortable 904 tok/s
- 09 Arc A310 4 GB · needs 0.7 GB · Q8_0 · comfortable 729 tok/s
- 10 Arc Pro A30M 4 GB · needs 0.7 GB · Q8_0 · comfortable 753 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Tesla C1080
Memory needed
0.7 GB
Fastest
72,398 tok/s
MatterGen is small enough at 46.8M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The smallest card that holds it is the Tesla C1080 with 4 GB, running it at Q8_0 and producing around 788 tokens per second.
At the other end, a B200 generates roughly 72,398 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
Background
MatterGen was published by Microsoft Research AI for Science, in United States of America, in January 2025. industry is the category the publisher falls under.
It works in Materials science, and is recorded as doing materials design, Crystal discovery.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. It is published under the microsoft organisation on Hugging Face.
Reading the throughput figures
The median result is around 2,032.9 tokens per second; 818 cards produce text faster than most people read it.
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.
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.
Training and provenance
Training it took roughly 2.7 × 10¹⁹ FLOP of computation, on NVIDIA A100 — a measure of what producing the model cost, not of how fast it answers.
Step by step
How to choose a GPU for MatterGen
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
The table lists every card that can hold MatterGen — around 0.7 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Match the context to your actual use
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason MatterGen stops fitting a card that seemed fine.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage MatterGen by squeezing it further than you would want.
-
04
Sort by speed
Ranking by tokens per second for MatterGen follows memory bandwidth, not core counts, which is why the B200 tops it at 72,398 tok/s.
-
05
Read the fit column last
The fit column separates cards that just manage MatterGen from those with room to spare. Buy for the second if the context might grow.
-
06
See what else that card runs
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond MatterGen.
Answers
MatterGen — common questions
Is MatterGen open source?
Its weights are published, so MatterGen 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 MatterGen have?
MatterGen has 46.8M parameters. "MatterGen contains 46.8M parameters" https://huggingface.co/microsoft/mattergen "The model architecture is based on GemNet (Gasteiger et al. 2021).". 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.
Who created MatterGen?
MatterGen was published by Microsoft Research AI for Science, based in United States of America, categorised as industry.
When was MatterGen released?
MatterGen was published in January 2025.
What is MatterGen used for?
MatterGen works in Materials science, and is recorded as handling materials design, Crystal discovery. These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download MatterGen?
Its weights are published under the microsoft organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train MatterGen?
Around 2.7 × 10¹⁹ FLOP, on NVIDIA A100. 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.
Can I run MatterGen 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. Our figures for MatterGen assume it is fully resident.
Would two GPUs run MatterGen faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run MatterGen alone, the case for pairing is weak.
Why does the quantisation differ between cards for MatterGen?
Because capacity varies, so does how hard MatterGen has to be squeezed — 1 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these MatterGen 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 43,439–115,837 tok/s on the B200 rather than a single number.
What GPU do I need to run MatterGen?
The smallest card in our catalogue that holds MatterGen is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 0.7 GB, and produces roughly 788 tokens per second. 818 cards in total can run it.
How fast is MatterGen on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 72,398 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 818 of the cards that can run MatterGen clear that.
How much VRAM does MatterGen need?
About 0.7 GB at Q8_0 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.
Can I run MatterGen on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 0.7 GB and generating roughly 13,484 tokens per second — a comfortable fit.
Can I run MatterGen on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 0.7 GB and generating roughly 8,257 tokens per second — a comfortable fit.
Can I run MatterGen on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 0.7 GB and generating roughly 10,226 tokens per second — a comfortable fit.
Can I run MatterGen on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 0.7 GB and generating roughly 12,127 tokens per second — a comfortable fit.
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.