Runyard / Run locally / Nemotron 3.5 Content Safety

Running Nemotron 3.5 Content Safety locally

Nemotron 3.5 Content Safety is a 4B-parameter dense model. Every parameter is read for every token generated, so both the memory it occupies and the speed it runs at follow directly from that one figure.

Weights: nvidia/Nemotron-3.5-Content-Safety · Context: 128K tokens · Published 2026-06-04 · Updated 2026-09-01

The short answer: at Q4_K_M, the quantisation most people actually run, Nemotron 3.5 Content Safety occupies roughly 2.2 GB of weights and needs about 4.2 GB of total VRAM once you add an 8K context window and runtime overhead. That puts it within reach of a Arc B580 (12 GB) and anything larger.

VRAM by quantisation

Quantisation trades precision for memory. Each row is Nemotron 3.5 Content Safety at 8K context, including the KV cache and ~1 GB of runtime overhead:

QuantWeightsTotal VRAMQuality
Q8_04.2 GB6.2 GBNear-lossless. Use when VRAM is free.
Q6_K3.3 GB5.3 GBVery close to FP16; the safe default if it fits.
Q5_K_M2.9 GB4.8 GBMild loss, noticeably smaller.
Q4_K_M2.2 GB4.2 GBThe sweet spot most people run.
Q3_K_M1.8 GB3.7 GBVisible degradation. Fallback only.

Below Q4 the returns turn sharply negative. Q3_K_M saves 0.5 GB over Q4_K_M but introduces errors you will notice in structured output and long-form reasoning. If Q4 does not fit, a smaller model at Q5 or Q6 almost always beats this one at Q3.

Which GPUs run it

Every current consumer card, against Nemotron 3.5 Content Safety at Q4_K_M. Throughput is estimated from memory bandwidth against the full weights:

GPUVRAMBandwidthRuns it?Est. speed
RTX 509032 GB1,792 GB/sYes — Q8_0~337 tok/s
RTX 409024 GB1,008 GB/sYes — Q8_0~190 tok/s
RTX 309024 GB936 GB/sYes — Q8_0~176 tok/s
RX 7900 XTX24 GB960 GB/sYes — Q8_0~181 tok/s
RTX 508016 GB960 GB/sYes — Q8_0~181 tok/s
RTX 5070 Ti16 GB896 GB/sYes — Q8_0~169 tok/s
RTX 5060 Ti 16GB16 GB448 GB/sYes — Q8_0~84 tok/s
RTX 4080 SUPER16 GB736 GB/sYes — Q8_0~139 tok/s
RTX 4070 Ti SUPER16 GB672 GB/sYes — Q8_0~126 tok/s
RTX 4060 Ti 16GB16 GB288 GB/sYes — Q8_0~54 tok/s
RX 9070 XT16 GB645 GB/sYes — Q8_0~121 tok/s
RTX 507012 GB672 GB/sYes — Q8_0~126 tok/s
Arc B58012 GB456 GB/sYes — Q8_0~86 tok/s

Notice that VRAM and bandwidth do not move together. The RTX 4060 Ti 16GB holds as much as an RTX 4080 SUPER but reads it at 288 GB/s against 736 GB/s, so it will load this model and then generate at roughly a third the speed. Capacity decides whether it runs; bandwidth decides whether you enjoy using it.

Getting it running

Fastest path, using Ollama:

ollama run nemotron-3-5-content-safety

For control over quantisation and context, pull the GGUF directly and serve it with llama.cpp:

huggingface-cli download nvidia/Nemotron-3.5-Content-Safety \
  --include "*Q4_K_M*.gguf" --local-dir ./models

llama-server -m ./models/*Q4_K_M*.gguf \
  --n-gpu-layers 999 \
  --ctx-size 8192

--n-gpu-layers 999 pushes everything onto the GPU; lower it until the model loads if you are short on memory. --ctx-size is worth tuning deliberately — this model supports up to 128K tokens, but the KV cache grows with it, and asking for the full window when you only need 8K can cost you several gigabytes for nothing.

Frequently asked questions

How much VRAM does Nemotron 3.5 Content Safety need?

About 4.2 GB at Q4_K_M with an 8K context window: 2.2 GB of weights plus KV cache and roughly 1 GB of runtime overhead. At Q8_0 it needs 6.2 GB, and at Q3_K_M it comes down to 3.7 GB.

What is the cheapest GPU that runs Nemotron 3.5 Content Safety?

The Arc B580 at 12 GB is the least expensive card that holds it at Q4_K_M, at around $249.

Can I run Nemotron 3.5 Content Safety on 8 GB of VRAM?

Yes — it fits at Q4_K_M with room for an 8K context.

Is Nemotron 3.5 Content Safety free to use commercially?

The weights are published openly on Hugging Face as nvidia/Nemotron-3.5-Content-Safety, but the licence is set by the model's publisher and varies — some are Apache 2.0 or MIT, others carry usage restrictions or revenue thresholds. Check the licence file on the model card before deploying it commercially.

Does quantisation make the model worse?

Measurably, but far less than people expect down to Q4. Q6_K is close enough to FP16 that differences are hard to detect; Q4_K_M costs a small amount of accuracy on reasoning and structured output; below Q4 the degradation becomes obvious. Running a larger model at Q4 generally beats a smaller one at Q8.

Why is my speed lower than the estimate here?

These figures assume the whole model sits in VRAM and the GPU sustains its rated bandwidth. Real throughput drops if any layers are offloaded to system RAM, if your context is long enough that attention starts to dominate, or if the card is thermally throttling. Prompt processing is also compute-bound rather than bandwidth-bound and follows different limits.

How much disk space do I need for Nemotron 3.5 Content Safety?

Budget 2 GB for the Q4_K_M GGUF, or 5 GB for Q8_0. Download the specific quantisation you want rather than the whole repository — most GGUF repos hold every variant, and cloning all of them wastes a great deal of space.

Related