How much VRAM does Nemotron-3 Super 120B-A12B need?
Nemotron · 120B params MoE · updated 2026-08-25
Headline answer
At bf16, reference 8K context, batch size 1: 244.2GB of VRAM. The smallest fitting configuration is 1× AMD MI355X 288GB.
VRAM by quantization
| Dtype | VRAM | Fits on |
|---|---|---|
| bf16 | 244.2GB | 1× AMD MI355X 288GB |
| fp8 | 126.6GB | 1× H200 NVL 141GB |
| awq | 68.2GB | 1× H100 PCIe 80GB |
| nvfp4 | 73.2GB | 1× H100 PCIe 80GB |
Context length sensitivity
Same model, same bf16 dtype, batch size 1 — VRAM at longer context windows.
| Context | VRAM (bf16) |
|---|---|
| 8K | 244.2GB |
| 32K | 244.4GB |
| 128K | 245.2GB |
Model facts
About Nemotron-3 Super 120B-A12B
At 120B total parameters, with only 12.0B active per token via mixture-of-experts routing, Nemotron-3 Super 120B-A12B sits firmly in the territory where quantization choice, not just raw parameter count, decides which GPU you end up buying or renting. In bf16 at a reference 8K context and batch size 1, the model needs 244.2GB of VRAM — computed the same way our interactive calculator computes it, from Nemotron's published architecture rather than a generic per-parameter estimate — and the smallest configuration that clears that bar is 1× AMD MI355X 288GB. Compare that to fp8, which roughly halves the weight footprint at essentially no measurable quality cost on most tasks, or AWQ and NVFP4, which push weight-only compression to 4 bits and can drop the requirement by roughly three-quarters relative to bf16 — often enough to move the model down an entire GPU tier or free up room for a much larger batch of concurrent requests. The full breakdown for all four dtypes is in the table above, alongside the exact GPU configuration each one unlocks. None of this accounts for context length, though: KV cache scales with how many tokens you keep resident, so a long-context deployment needs meaningfully more headroom than this 8K reference — the context-sensitivity table shows the same bf16 model at 32K and 128K wherever its native window supports it, so you can see the real cost of long-context serving before you commit to hardware.
Frequently asked questions
How much VRAM does Nemotron-3 Super 120B-A12B need?
At bf16, reference 8K context and batch size 1, Nemotron-3 Super 120B-A12B needs 244.2GB of VRAM. The smallest fitting configuration we find is 1× AMD MI355X 288GB.
How many parameters does Nemotron-3 Super 120B-A12B have?
Nemotron-3 Super 120B-A12B has 120B total parameters, with 12.0B active per token via mixture-of-experts routing.
Does quantization reduce Nemotron-3 Super 120B-A12B's VRAM requirement?
Yes — switching from bf16 to fp8 brings the total down to 126.6GB, and weight-only int4 formats (AWQ, NVFP4) go further still. See the per-dtype table above for exact numbers.
Where do these VRAM numbers come from?
They're computed by the same calculator engine behind our interactive GPU calculator, from the model's published architecture (layers, hidden size, attention heads, KV cache config) — not a generic per-parameter estimate.
Methodology: VRAM figures are computed by the same calculator engine behind our interactive GPU calculator, from Nemotron-3 Super 120B-A12B's published architecture (layer count, hidden size, attention heads, KV cache configuration) — not a generic per-parameter estimate. Reference scenario: batch size 1, vLLM framework, fp16 KV cache. Page last updated 2026-08-25. These are engineering estimates, not a guarantee — always validate against your actual serving framework and workload before committing to hardware.
Size a full deployment — concurrency, framework, quantization — in the calculator →