Nemotron-H 56B 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
Smallest card that fits
FirePro S9170
32 GB · Q3_K_M · 5.1 tok/s
Fastest card
B200
60.5 tok/s · 180 GB
Which GPUs can run Nemotron-H 56B?
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.
92 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
60.5
tok/s
36–97 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 60.7 GB | Q8_0 | Comfortable |
|
60.5
tok/s
36–97 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 60.7 GB | Q8_0 | Comfortable |
|
48.3
tok/s
29–77 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 60.7 GB | Q8_0 | Comfortable |
|
48.3
tok/s
29–77 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 60.7 GB | Q8_0 | Comfortable |
|
38.6
tok/s
23–62 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 60.7 GB | Q8_0 | Comfortable |
|
38.2
tok/s
23–61 · low confidence |
DRIVE A100 PROD NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 28.1 GB | Q3_K_M | Tight |
|
38.2
tok/s
23–61 · low confidence |
GRID A100A NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 28.1 GB | Q3_K_M | Tight |
|
37.0
tok/s
22–59 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 60.7 GB | Q8_0 | Comfortable |
|
37.0
tok/s
22–59 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 60.7 GB | Q8_0 | Comfortable |
|
36.5
tok/s
22–58 · low confidence |
GeForce RTX 5090 NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 28.1 GB | Q3_K_M | Tight |
|
36.5
tok/s
22–58 · low confidence |
GeForce RTX 5090 D NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 28.1 GB | Q3_K_M | Tight |
|
35.4
tok/s
21–57 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 60.7 GB | Q8_0 | Comfortable |
|
31.4
tok/s
19–50 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 60.7 GB | Q8_0 | Comfortable |
|
31.4
tok/s
19–50 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 60.7 GB | Q8_0 | Comfortable |
|
31.4
tok/s
19–50 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 60.7 GB | Q8_0 | Comfortable |
|
29.8
tok/s
18–48 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 60.7 GB | Q8_0 | Comfortable |
|
27.2
tok/s
16–44 · low confidence |
A100 PCIe 40 GB NVIDIA | 40 GB | 1,560 GB/s | Jun 2020 | 34.6 GB | Q4_K_M | Tight |
|
27.2
tok/s
16–44 · low confidence |
A100 SXM4 40 GB NVIDIA | 40 GB | 1,560 GB/s | May 2020 | 34.6 GB | Q4_K_M | Tight |
|
27.2
tok/s
16–44 · low confidence |
A800 PCIe 40 GB NVIDIA | 40 GB | 1,560 GB/s | Nov 2022 | 34.6 GB | Q4_K_M | Tight |
|
25.4
tok/s
15–41 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 60.7 GB | Q8_0 | Comfortable |
|
25.4
tok/s
15–41 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 60.7 GB | Q8_0 | Tight |
|
25.4
tok/s
15–41 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 60.7 GB | Q8_0 | Comfortable |
|
25.4
tok/s
15–41 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 60.7 GB | Q8_0 | Comfortable |
|
25.4
tok/s
15–41 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 60.7 GB | Q8_0 | Tight |
|
25.3
tok/s
15–40 · low confidence |
GRID A100B NVIDIA | 48 GB | 1,870 GB/s | May 2020 | 41.1 GB | Q5_K_M | Tight |
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
- NVIDIA
- Organisation type
- Industry
- Country
- United States of America
- Published
- 14 April 2025
- Authors
- NVIDIA: Aaron Blakeman, Aarti Basant, Abhinav Khattar, Adithya Renduchintala, Akhiad Bercovich, Aleksander Ficek, Alexis Bjorlin, Ali Taghibakhshi, Amala Sanjay Deshmukh, Ameya Sunil Mahabaleshwarkar, Andrew Tao, Anna Shors, Ashwath Aithal, Ashwin Poojary, Ayush Dattagupta, Balaram Buddharaju, Bobby Chen, Boris Ginsburg, Boxin Wang, Brandon Norick, Brian Butterfield, Bryan Catanzaro, Carlo del Mun…
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Question answering, Translation, Quantitative reasoning, Code generation
- Numerical format
- FP8
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
- 56B
- Training data
- tokens
- Epochs
- 1
- Batch size
- 6,291,456
Model Architecture Architecture Type: Hybrid Mamba-Transformer Network Architecture: Nemotron-H This model has 56B model parameters.
"We trained Nemotron-H-8B-Base on a token horizon of 15 trillion tokens and Nemotron-H-56B-Base on a token horizon of 20 trillion tokens. We used a sequence length of 8192 and global batch size of 768 (6291456 tokens per batch)."
"We used a sequence length of 8192 and global batch size of 768 (6291456 tokens per batch)."
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
- 6.7 × 10²⁴ FLOP
- How it was established
- Operation counting
6 FLOP / parameter / token * 56 * 10^9 parameters * 20 * 10^12 tokens = 6.72e+24 FLOP
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
- 6,144
- Power draw
- 8.4 MW
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 (non-commercial)
- Training code
- Unreleased
- Hugging Face
- nvidia
https://huggingface.co/nvidia/Nemotron-H-56B-Base-8K nvidia-internal-scientific-research-and-development-model-license
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.
- Reference
- Nemotron-H: A Family of Accurate and Efficient Hybrid Mamba-Transformer Models
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs for Nemotron-H 56B
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 60.5 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 60.5 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 48.3 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 48.3 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 38.6 tok/s
- 06 DRIVE A100 PROD 32 GB · 1,870 GB/s · Q3_K_M 38.2 tok/s
- 07 GRID A100A 32 GB · 1,870 GB/s · Q3_K_M 38.2 tok/s
- 08 H200 NVL 141 GB · 4,890 GB/s · Q8_0 37.0 tok/s
- 09 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 37.0 tok/s
- 10 GeForce RTX 5090 32 GB · 1,790 GB/s · Q3_K_M 36.5 tok/s
The smallest GPUs that still run Nemotron-H 56B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Radeon AI PRO 9600D 32 GB · needs 28.1 GB · Q3_K_M · tight 9.2 tok/s
- 02 Radeon AI PRO R9700S 32 GB · needs 28.1 GB · Q3_K_M · tight 10.3 tok/s
- 03 Radeon AI PRO R9700 32 GB · needs 28.1 GB · Q3_K_M · tight 10.3 tok/s
- 04 RTX PRO 4500 Blackwell 32 GB · needs 28.1 GB · Q3_K_M · tight 18.3 tok/s
- 05 GeForce RTX 5090 32 GB · needs 28.1 GB · Q3_K_M · tight 36.5 tok/s
- 06 GeForce RTX 5090 D 32 GB · needs 28.1 GB · Q3_K_M · tight 36.5 tok/s
- 07 RTX 5000 Ada Generation 32 GB · needs 28.1 GB · Q3_K_M · tight 11.8 tok/s
- 08 Radeon PRO W7800 32 GB · needs 28.1 GB · Q3_K_M · tight 9.2 tok/s
- 09 Jetson AGX Orin 32 GB 32 GB · needs 28.1 GB · Q3_K_M · tight 4.2 tok/s
- 10 Radeon PRO V620 32 GB · needs 28.1 GB · Q3_K_M · tight 8.2 tok/s
What the numbers mean
The hardware side
Minimum card
FirePro S9170
Memory needed
28.1 GB
Fastest
60.5 tok/s
With 56B parameters, Nemotron-H 56B lands in the range a serious desktop card can handle once the weights are compressed. 92 of the cards we track can run it.
At the low end, a FirePro S9170 handles it — 32 GB, at Q3_K_M, for about 5.1 tokens per second.
A B200 is the fastest we calculate for it: about 60.5 tokens per second, from 8,000 GB/s of memory bandwidth.
Background
Nemotron-H 56B was published by NVIDIA, in United States of America, in April 2025. The organisation is categorised as industry.
It works in Language, and is recorded as doing language modeling/generation, Question answering, Translation, Quantitative reasoning, Code generation.
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 nvidia organisation on Hugging Face.
Reading the throughput figures
Half the cards that hold it manage more than 15.4 tokens per second, and 72 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.
Training and provenance
Producing it required around 6.7 × 10²⁴ FLOP of arithmetic, on NVIDIA H100 SXM5 80GB, which is a statement about the training budget rather than about inference.
Step by step
How to choose a GPU for Nemotron-H 56B
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
Look at what Nemotron-H 56B actually needs — around 28.1 GB at Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
-
02
Decide how long your conversations run
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Nemotron-H 56B.
-
03
Choose how far you will compress it
Compression is what makes Nemotron-H 56B fit smaller cards, at some cost in accuracy — Q3_K_M on the smallest card that fits. A minimum quality removes the ones that go too far.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for Nemotron-H 56B. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 60.5 tok/s.
-
05
Look at the headroom, not just the fit
A tight fit runs Nemotron-H 56B 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 Nemotron-H 56B.
Answers
Nemotron-H 56B — common questions
Can I run Nemotron-H 56B 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 Nemotron-H 56B is rarely worth using — the nearest miss we calculate is short by 9.4 GB. Every figure here assumes the whole model is on the card.
Would two GPUs run Nemotron-H 56B faster?
Two cards buy memory rather than speed. That matters for Nemotron-H 56B only if one card cannot hold it — 92 can, so a second adds little.
Why does the quantisation differ between cards for Nemotron-H 56B?
Because capacity varies, so does how hard Nemotron-H 56B has to be squeezed — 5 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these Nemotron-H 56B 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 36–97 tok/s on the B200 rather than a single number.
What GPU do I need to run Nemotron-H 56B?
The smallest card in our catalogue that holds Nemotron-H 56B is the FirePro S9170, with 32 GB of memory. It runs the model at Q3_K_M using about 28.1 GB, and produces roughly 5.1 tokens per second. 92 cards in total can run it.
How fast is Nemotron-H 56B on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 60.5 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 72 of the cards that can run Nemotron-H 56B clear that.
How much VRAM does Nemotron-H 56B need?
About 28.1 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 Nemotron-H 56B open source?
Its weights are published, so Nemotron-H 56B 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 Nemotron-H 56B have?
Nemotron-H 56B has 56B parameters. Model Architecture Architecture Type: Hybrid Mamba-Transformer Network Architecture: Nemotron-H This model has 56B model parameters. 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 Nemotron-H 56B?
Nemotron-H 56B was published by NVIDIA, based in United States of America, categorised as industry.
When was Nemotron-H 56B released?
Nemotron-H 56B was published in April 2025.
What is Nemotron-H 56B used for?
Nemotron-H 56B works in Language, and is recorded as handling language modeling/generation, Question answering, Translation, Quantitative reasoning, Code 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.
Where can I download Nemotron-H 56B?
Its weights are published under the nvidia 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 Nemotron-H 56B?
Around 6.7 × 10²⁴ FLOP, on 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.
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.