What GPU do I need to run nvidia/NVIDIA-Nemotron-Nano-9B-v2-FP8?

8.9B parameters, published in F8_E4M3. View on Hugging Face

8.9B
Parameters
F8_E4M3
Native precision
NemotronHForCausalLM
Architecture
text-generation
Pipeline

NVIDIA-Nemotron-Nano-9B-v2-FP8 is published by nvidia on Hugging Face, with 121,282 downloads and 9 likes to date. It's a NemotronHForCausalLM model built for text-generation, published natively in F8_E4M3.

VRAM required & cheapest live GPU fit

Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.

PrecisionWeight sizeRequired VRAMCheapest live fitGPUs neededEst. $/hr (full fit)
FP8 (native)8.3 GB9.9 GBRTX 5060 Ti1$0.188/hr
INT4 (quantized)4.1 GB5.0 GBRTX 30601$0.110/hr

A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.

INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.

Cheapest way to run NVIDIA-Nemotron-Nano-9B-v2-FP8 at its published (F8_E4M3) precision: 1× RTX 5060 Ti, at $0.188/hr per GPU ($0.188/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.

NVIDIA-Nemotron-Nano-9B-v2-FP8: KV cache by context length

The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.

Hybrid: only the full-attention layers cache per token; the other layers keep a fixed-size state. Cached per token: 16,384 bytes at 16-bit.

ContextKV cache, one sequence
4K0.06 GB
32K0.50 GB
128K2.0 GB

Computed from the layer, head and window counts in the model's own configuration (nvidia/NVIDIA-Nemotron-Nano-9B-v2-FP8), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.

NVIDIA-Nemotron-Nano-9B-v2-FP8: common questions

Does NVIDIA-Nemotron-Nano-9B-v2-FP8 fit on a 12 GB GPU?

Yes. At FP8 (native) it needs 9.9 GB of VRAM, so a 12 GB card holds it with 2.1 GB to spare. An 8 GB card is not enough for it at FP8 (native).

Is NVIDIA-Nemotron-Nano-9B-v2-FP8 already quantized?

Yes. It is published in FP8, one byte per parameter, so the 9.9 GB figure is already a quantized footprint rather than a full-precision one. Only INT4 goes below it, at 5.0 GB. A GPU without FP8 tensor cores cannot run it as published, which is why cards here are matched on precision support and not on VRAM alone.

What is the least VRAM NVIDIA-Nemotron-Nano-9B-v2-FP8 can run in?

5.0 GB, at INT4 (quantized), which fits a 6 GB card, against 9.9 GB at FP8 (native). That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.

Does quantizing NVIDIA-Nemotron-Nano-9B-v2-FP8 lower the GPU bill?

Yes. At FP8 (native) the cheapest live fit is one RTX 5060 Ti at $0.188/hr. At INT4 (quantized) it drops to one RTX 3060 at $0.110/hr, provided a quantized checkpoint exists for it.

Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.

More Nemotron Nano models

All 4 Nemotron Nano models: VRAM and GPU requirements

Lineage

Based on NVIDIA-Nemotron-Nano-9B-v2.

Alternatives at this size

Other models for text-generation within about a third of NVIDIA-Nemotron-Nano-9B-v2-FP8's 8.9B parameters, from other model lines.

More on NVIDIA-Nemotron-Nano-9B-v2-FP8

Related reading: H100 pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.

Submit the job. Everything after that is ours.

Sign up in 60 seconds. Pay for the GPU minutes you actually use.

© 2026 Aquanode. All rights reserved.

All trademarks, logos and brand names are the property of their respective owners.