Can I Run Nemotron 70B on 96 GB system RAM?

Superseded model. Nemotron 70B has been superseded by Nemotron 3 Super. This page is kept for reference; the newer family is a better starting point. View Nemotron 3 Super →

Written by Jakub Rusinowski · Last updated October 15, 2024

Technically yes, but not recommended

It loads, but it is not worth running — Nemotron 70B Instruct at Q6_K fits in 96 GB system RAM's 76.8 GB, yet the memory bandwidth limits it to ~1.1 tok/s (estimated), well below usable interactive speed.

Confidence: high · Recommended quantization: Q6_K · Estimated speed: ~1.1 tok/s

Buy This HardwareApple MacBook Pro M5 Pro — Launch MSRP: $1,999 Deploy in the Cloud NowNVIDIA A100 80GB on RunPod — from $1.39/hr · rate checked 2026-07

or compare on Vast.ai from $0.77/hr (typical low · varies)

As an Amazon Associate we earn from qualifying purchases. Cloud GPU links are referral links — we may earn a commission at no extra cost to you.

96 GB system RAM — what it gives a model

Usable memory for models	76.8 GB
Memory bandwidth	90 GB/s

Nemotron 70B on 96 GB system RAM: memory by quantization

Quant	Memory needed	Fits 76.8 GB?	Max context	Est. speed	Download
F16	144.7 GB	✗ No	—	—	141.2 GB
Q8_0	78.5 GB	✗ No	—	—	75 GB
Q6_K	61.4 GB	✓ Yes	32K	~1.1 tok/s	57.9 GB
Q5_K_M	53.5 GB	✓ Yes	64K	~1.3 tok/s	50 GB
Q4_K_M	46.1 GB	✓ Yes	64K	~1.5 tok/s	42.6 GB
Q3_K_M	33.6 GB	✓ Yes	64K	~2.1 tok/s	30.1 GB
Q2_K	26.7 GB	✓ Yes	64K	~2.7 tok/s	23.2 GB

What to watch out for

At ~1.1 tok/s this loads but is too slow for interactive use — expect roughly 55 seconds per 60 tokens.
These figures assume CPU-only inference. Any discrete GPU, even an 8 GB one, will be several times faster for models that fit in its VRAM.

Recommended setup

llama.cpp (CPU build) or Ollama — both run without a GPU

How these numbers are calculated

Memory need = quantized weights + KV cache at 8,192 tokens (f16) + 0.8 GB runtime overhead.
76.8 GB of the 96 GB is treated as usable for model weights (80% — the rest is the OS and running applications).
DDR5-5600 dual channel at 89.6 GB/s peak. CPU decode is assumed to sustain 35% of that peak, because CPU inference is not purely bandwidth-bound — it also spends real time in compute and thread synchronisation. This figure is an assumption, not a fitted constant: no CPU measurement is in the calibration set.
CPU-only inference: no GPU is assumed. A GPU of any size will beat these figures substantially.
Throughput is a memory-bandwidth roofline estimate, not a measurement. It is labelled "estimated" everywhere it appears.
KV cache is computed from this model's published attention configuration.

FAQ