Nemotron 3 Super GPU requirements: 61.8 GB at 4-bit, 247 GB at BF16
Nemotron 3 Super needs 247 GB of GPU memory for its weights at BF16, 124 GB at FP8 and 61.8 GB at 4-bit, plus 0.27 GB of KV cache for a 32K context. The cheapest node that runs it here is 1× A100 PCIe 80GB at 4-bit, for $0.09 an hour on spot.
Weights plus a 32K 16-bit KV cache, with 10% of the node's memory kept free. Billed per minute.
- Parameters
- 120B12B active per token
- Weights, 4-bit
- 61.8 GBBF16: 247 GB
- KV cache, 32K
- 0.27 GBOne sequence, 16-bit cache
- Context window
- 256KNative
How much VRAM Nemotron 3 Super needs, format by format.
Weights are parameters × bytes per parameter. Each context column adds the KV cache of one sequence of that length.
| Format | Weights | + 8Kcontext | + 32Kcontext | + 128Kcontext | + 256Kcontext | Cheapest node, 32K |
|---|---|---|---|---|---|---|
| BF16Published weights, fine-tuning | 247 GB | 247 GB | 247 GB | 248 GB | 249 GB | 4× A100 PCIe 80GB · $0.36/h |
| FP8Hopper, Ada, Blackwell, MI300 | 124 GB | 124 GB | 124 GB | 125 GB | 126 GB | 4× L40 · $0.36/h |
| 4-bitAWQ, GPTQ, GGUF Q4 | 61.8 GB | 61.9 GB | 62.1 GB | 62.9 GB | 64.0 GB | 1× A100 PCIe 80GB · $0.09/h |
The serving engine adds its own buffers, and an 8-bit KV cache halves the context columns. We keep 10% of a node's memory free when we say a model fits. Speed is a separate question: it follows memory bandwidth and, for a mixture of experts, the active parameters.
GPUs that run Nemotron 3 Super, cheapest first.
For each format, the smallest node of each GPU model that holds the weights and a 32K context, sorted by spot price. One row per GPU model; larger nodes of the same GPU work too.
| Format | GPU | GPU memory | Spot | On-demand | 730 h spot | Action |
|---|---|---|---|---|---|---|
| 4-bit | 1× A100 PCIe 80GBAmpere · 62.1 GB needed | 80 GB | $0.09 | $0.19 | $65.70 | Deploy |
| 4-bit | 2× A40Ampere · 62.1 GB needed | 96 GB | $0.12 | $0.18 | $87.60 | Deploy |
| 4-bit | 2× A100 40GBAmpere · 62.1 GB needed | 80 GB | $0.18 | $0.34 | $131.40 | Deploy |
| 4-bit | 2× L40Ada Lovelace · 62.1 GB needed | 96 GB | $0.18 | $0.38 | $131.40 | Deploy |
| FP8 | 4× L40Ada Lovelace · 124 GB needed | 192 GB | $0.36 | $0.76 | $262.80 | Deploy |
| FP8 | 4× RTX 6000 AdaAda Lovelace · 124 GB needed | 192 GB | $0.36 | $0.76 | $262.80 | Deploy |
| FP8 | 2× RTX PRO 6000 BlackwellBlackwell · 124 GB needed | 192 GB | $0.38 | $0.78 | $277.40 | Deploy |
| FP8 | 4× L40SAda Lovelace · 124 GB needed | 192 GB | $0.60 | $1.00 | $438.00 | Deploy |
| BF16 | 4× A100 PCIe 80GBAmpere · 247 GB needed | 320 GB | $0.36 | $0.76 | $262.80 | Deploy |
| BF16 | 8× A40Ampere · 247 GB needed | 384 GB | $0.48 | $0.72 | $350.40 | Deploy |
| BF16 | 8× A100 40GBAmpere · 247 GB needed | 320 GB | $0.72 | $1.36 | $525.60 | Deploy |
| BF16 | 8× L40Ada Lovelace · 247 GB needed | 384 GB | $0.72 | $1.52 | $525.60 | Deploy |
Spot capacity can be reclaimed with a 2-minute notice; for a live endpoint, use on-demand. How spot works · serving a language model.
What a long context costs in memory.
Hybrid Mamba-Transformer: 8 attention layers (2 KV heads of 128) among 88 blocks; the Mamba layers keep a fixed-size state.
| Context | KV cache, 1 sequence | 8 sequences |
|---|---|---|
| 8K tokens | 0.07 GB | 0.54 GB |
| 32K tokens | 0.27 GB | 2.15 GB |
| 128K tokens | 1.07 GB | 8.59 GB |
| 256K tokens | 2.15 GB | 17.2 GB |
Serving several users
KV cacheEvery concurrent request keeps its own cache, so memory for context grows with users × context length. A server batching 8 requests of 32K needs eight times the single-sequence figure — 2.15 GB here.
- Recommended node1× A100 PCIe 80GB
- Weights at 4-bit61.8 GB
- Context that fits, 1 sequence256K
Paged attention (vLLM, SGLang) allocates the cache in blocks as requests grow, so a node holds more short requests than the worst case suggests.
Nemotron 3 Super, as published.
- Developer
- NVIDIAHybrid Mamba-Transformer mixture of experts
- Parameters
- 120B total, 12B active per token124B in the published checkpoint (embedding tables, prediction or vision modules included); memory figures use this count
- Architecture
- Mixture of experts, 88 layersHybrid Mamba-Transformer: 8 attention layers (2 KV heads of 128) among 88 blocks; the Mamba layers keep a fixed-size state
- Context window
- 262,144 tokensAs set in the published configuration
- Published format
- BF16, 247 GB
- Licence
- Custom licence (see the model card)
- Released
- 10 March 2026
- Source
- nvidia/NVIDIA-Nemotron-3-Super-120B-A12B-BF16config.json read 26 October 2026
Serve it with vLLM
template: vLLMOn 1× A100 PCIe 80GB, from the instance terminal:
$ vllm serve nvidia/NVIDIA-Nemotron-3-Super-120B-A12B-BF16 \ --tensor-parallel-size 1 \ --max-model-len 32768
Very recent architectures need a recent vLLM; the model card gives the minimum version and any extra flags.
Nemotron 3 Super on a GPU — the questions that come up
How much VRAM does Nemotron 3 Super need?
For the weights alone: 247 GB at BF16, 124 GB at FP8 and 61.8 GB at 4-bit. Add 0.27 GB of KV cache for one 32K-token context, or 2.15 GB at the full 256K window, and keep about 10% of the memory free for activations.
Can Nemotron 3 Super run on a single GPU?
One RTX 4090 (24 GB): no. One RTX 5090 (32 GB): no. One H100 SXM (80 GB): yes, at 4-bit. One H200 SXM (141 GB): yes, at FP8. One B200 SXM (180 GB): yes, at FP8. Those answers assume a 32K context and the widest format that still fits.
What is the cheapest way to run Nemotron 3 Super?
Here, 1× A100 PCIe 80GB at 4-bit: $0.09 per hour on spot and $0.19 on-demand, billed per minute — $65.70 for a 730-hour month on spot. That node has 80 GB of GPU memory for the 62.1 GB this setup needs.
Does Nemotron 3 Super need less memory because only 12B parameters are active?
No. A mixture-of-experts model routes each token through a few experts, but every expert has to be resident in GPU memory, so the memory bill follows the 120B total. What the 12B active parameters change is the work per token: generation reads far less of the weights each step than a dense model of the same size would, which is why it is fast for its size.
Which format should I run it in?
BF16 keeps the published weights untouched and is the format for fine-tuning. FP8 halves the memory and runs in hardware on Hopper, Ada, Blackwell and MI300-class GPUs. 4-bit quantisation (AWQ, GPTQ, GGUF) quarters it, at a quality cost that is larger on small models than on big ones; check it against your own evaluation before relying on it.
How do I deploy it?
Pick the node in the table above and launch it with the vLLM template; the model downloads from Hugging Face (nvidia/NVIDIA-Nemotron-3-Super-120B-A12B-BF16) on first start. Spread the weights over the node with --tensor-parallel-size equal to the GPU count, and set --max-model-len to the context you need. New architectures need a recent vLLM: check the model card for the minimum version.
Sizing another model? GPU requirements for 64 open models · serving a language model · fine-tuning.
Nemotron 3 Super on 1× A100 PCIe 80GB for $0.09 an hour.
Launch the node with the vLLM template, point it at nvidia/NVIDIA-Nemotron-3-Super-120B-A12B-BF16, stop it when you are done. Prepaid, billed by the minute.
Billed per minute from the moment the instance is reachable. Minimum credit $30, no subscription.