on

Can the NVIDIA RTX Spark N1X (5120-core GPU) (32 GB) run Nemotron Labs Dory 1.0 4B?

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

Yes, it runs great

Runs great. At Q8_0 it needs about 6.6 GB of 16.0 GB usable, with an estimated speed of 47.1 tok/s.

Best quant
Q8_0
Generation speed
47.1 tok/s
Prompt processing
4,342 tok/s
First token (1K prompt)
0.3 s
Largest safe context
168K

Best app to run it on the NVIDIA RTX Spark N1X (5120-core GPU) (32 GB)

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open Nemotron Labs Dory 1.0 4B in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

Want an agent? Nemotron Labs Dory 1.0 4B 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, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Nemotron Labs Dory 1.0 4B

Ollama

Not in the Ollama library yet. Mainline llama.cpp (which Ollama and LM Studio build on) does not support the Dory architecture yet, so NVIDIA’s GGUF needs a llama.cpp build from PR #30306. vLLM has merged support (PR #60149).

Quantized files · GGUF

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

huggingface.co/nvidia/NVIDIA-Nemotron-Labs-Dory1.0-4B-GGUF (opens in a new tab)

ollama run hf.co/nvidia/NVIDIA-Nemotron-Labs-Dory1.0-4B-GGUF

Original weights · Hugging Face

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

huggingface.co/nvidia/NVIDIA-Nemotron-Labs-Dory1.0-4B-BF16 (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 68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q8_0, 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 Runs great
How well it runs on the NVIDIA RTX Spark N1X (5120-core GPU) (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.30.6 / 45
Memory fitFull marks when the model fits in the share of unified memory the GPU can use; 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.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.9.5 / 15
Match score80.1 / 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 NVIDIA RTX Spark N1X (5120-core GPU) (32 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 3.9 GB 16.0 GB 152 tok/s Runs great 47Fair quality (C) · 47 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 4.3 GB 16.0 GB 120 tok/s Runs great 57Good quality (B) · 57 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 4.8 GB 16.0 GB 92.5 tok/s Runs great 64Good quality (B) · 64 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 75/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q5_K_M 5.2 GB 16.0 GB 76.4 tok/s Runs great 65Good quality (B) · 65 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 5.6 GB 16.0 GB 64.2 tok/s Runs great 67Good quality (B) · 67 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 6.6 GB 16.0 GB 47.1 tok/s Runs great 68Good quality (B) · 68 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 10.3 GB 16.0 GB 21.7 tok/s Runs well 68Good quality (B) · 68 of 100: how capable the model is at F16, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. 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?