on

Can the Intel Xeon W-2100 series NAS (32 GB) run OpenReasoning Nemotron 14B?

65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly

Slow. At Q6_K it needs about 16.4 GB of 26.2 GB usable, with an estimated speed of 3.1 tok/s.

Best quant
Q6_K
Generation speed
3.1 tok/s
Prompt processing
24.4 tok/s
First token (1K prompt)
42.0 s
Largest safe context
56K

Best app to run it on the Intel Xeon W-2100 series NAS (32 GB)

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Usually the first to support new model architectures.
llama-server -hf bartowski/nvidia_OpenReasoning-Nemotron-14B-GGUF:Q6_K

Want an agent? OpenReasoning Nemotron 14B supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

How we choose: the files published for this model, which apps run in a container on a NAS without a graphics card (models run on its processor), and whether the model fits fully in the memory models can use. Details.

Download OpenReasoning Nemotron 14B

Recommended for the Intel Xeon W-2100 series NAS (32 GB): Q6_K. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q6_K file (opens in a new tab)

huggingface.co/bartowski/nvidia_OpenReasoning-Nemotron-14B-GGUF (opens in a new tab)

ollama run hf.co/bartowski/nvidia_OpenReasoning-Nemotron-14B-GGUF:Q6_K

Original weights · Hugging Face

Full-precision files from NVIDIA, for fine-tuning, vLLM, Transformers.

huggingface.co/nvidia/OpenReasoning-Nemotron-14B (opens in a new tab)

No sign-in needed.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q6_K, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Slow
How well it runs on the Intel Xeon W-2100 series NAS (32 GB): speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.29.4 / 45
Memory fitFull marks when the model fits in the share of the NAS’s memory that models can use (the rest stays with the NAS system and its storage services); fewer when it goes past that limit.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.4.2 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.14.4 / 15
Match score73.0 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the Intel Xeon W-2100 series NAS (32 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 10.2 GB 26.2 GB 7.3 tok/s Slow 46Fair quality (C) · 46 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 61/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 11.5 GB 26.2 GB 5.7 tok/s Slow 55Good quality (B) · 55 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 13.3 GB 26.2 GB 4.4 tok/s Slow 62Good quality (B) · 62 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 14.8 GB 26.2 GB 3.7 tok/s Slow 64Good quality (B) · 64 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 16.4 GB 26.2 GB 3.1 tok/s Slow 65Good quality (B) · 65 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 20.0 GB 26.2 GB 2.3 tok/s Very slow 66Good quality (B) · 66 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 73/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 33.8 GB 26.2 GB — Won't run 66Good quality (B) · 66 of 100: how capable the model is at F16, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab) Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?