How much VRAM does Nemotron 3 Ultra 550B A55B (MoE) need at Q4_K_M? NVIDIA 1M Mamba-2

By TechCompare · Updated · How we check

Nemotron 3 Ultra 550B at Q4_K_M is a 353 GB resident deployment for 1M context. The Mamba-2 layers keep the cache to 13 GB, so the 308 GB of weights are most of the bill.

Calculator

Estimated VRAM required

353 GB

550B params at Q4_K_M, 1,048,576 token context, batch 1, inference.

Weights
308 GB
KV cache
12.9 GB
Overhead
32.1 GB

Estimate accuracy: Weights within ~2%. KV cache within ~5% for standard GQA models, ~10% for MLA or hybrid state estimates. Real VRAM may vary with framework (vLLM vs llama.cpp vs Transformers), Flash Attention, and driver overhead.

Hardware that fits

Apple entries show installed unified memory separately from a model budget based on an 8 GB reserve. That budget is a planning heuristic, not a fixed hardware limit.

No single GPU in our catalog has enough memory. Multi-GPU or CPU offload required.

Nemotron 3 Ultra 550B at Q4_K_M with native 1M context needs about 353 GB of VRAM with all experts resident. NVIDIA's hybrid Mamba-2 plus MoE model activates 55B parameters per token from a 550B total pool.

Only 12 of 108 transformer blocks carry attention and the other 48 are Mamba-2 state-space layers with zero key-value cache. Those 55B active params don't shrink what has to stay loaded, because different tokens pick different experts.

How this is calculated

The 550B parameter pool requires 308 GB of weights at Q4_K_M. The architecture is a hybrid: 12 attention layers, 48 Mamba-2 state-space layers, and 48 MoE expert blocks.

Only the 12 attention layers contribute to the key-value cache, which is just 13 GB at the full 1M context with 2 KV heads at head_dim 128. The Mamba-2 layers maintain a fixed recurrent state instead of growing a cache. Activation and software overhead adds about 32 GB.

Verdict

Resident mode needs 5 cards of 80 GB or 3 H200 cards of 141 GB with NVLink. The Mamba-2 layers are what keep the cache to 13 GB: where a pure-attention 108-layer model would need 100 GB-plus of cache at 1M context, the 48 Mamba layers maintain a fixed recurrent state instead.

More Nemotron scenarios

Kimi K3.1 Pro at Q4_K_M
A 2.78T expert pool with 24 latent attention layers and fixed state in the other 69.
View details
Mistral Large 4 at Q4_K_M
A 1T expert pool with 63 latent cache owners and 44 layers that also store an index key.
View details
Muse Spark Open at Q4_K_M
Only 16 of its 62 layers grow with context, and the other 46 hold a 2,048 token window.
View details

Frequently asked questions

Why is Nemotron 3 Ultra's key-value cache so small?
48 of 108 transformer blocks are Mamba-2 state-space layers. Mamba-2 maintains a fixed-size recurrent state instead of growing a key-value cache with context length. Only the 12 attention layers contribute to the cache. At 1M context the cache is about 13 GB, roughly an order of magnitude smaller than a pure-attention model of the same layer count.
How does Nemotron 3 Ultra compare to Nemotron 3 Super?
Super is 120B total with 12B active. Only 8 of its 88 blocks are attention layers, at 2 KV heads, so its cache is 9 GB at 1M context. Ultra is 550B total with 55B active, 12 attention layers at 2 KV heads and 48 Mamba-2 layers, which gives a 13 GB cache at 1M context. Ultra's cache is a bit larger because it has more attention layers, but the weights drive the difference: Ultra has 4.6x the parameter count, so its resident total is 353 GB versus Super's 83 GB.
What does a high volume focus change about how you run these models?
It means the reference VRAM numbers assume datacenter cards and many concurrent requests, not an interactive session on a workstation. A solo user on a single card gets the memory story but not the throughput story, which is where a shared deployment pays off.