on

Can the NVIDIA RTX Spark N1X (6144-core GPU) (128 GB) run Kimi Dev 72B?

79Great quality (A) · 79 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly

Slow. At Q6_K it needs about 71.1 GB of 102 GB usable, with an estimated speed of 3.5 tok/s.

Best quant
Q6_K
Generation speed
3.5 tok/s
Prompt processing
285 tok/s
First token (1K prompt)
3.6 s
Largest safe context
101K

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

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve moonshotai/Kimi-Dev-72B
  • LM Studio Point-and-click: search, download and chat in one window.
  • llama.cpp Usually the first to support new model architectures.

Want an agent? Kimi Dev 72B 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 Kimi Dev 72B

Recommended for the NVIDIA RTX Spark N1X (6144-core GPU) (128 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 files (opens in a new tab)

huggingface.co/unsloth/Kimi-Dev-72B-GGUF (opens in a new tab)

ollama run hf.co/unsloth/Kimi-Dev-72B-GGUF

Original weights · Hugging Face

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

huggingface.co/moonshotai/Kimi-Dev-72B (opens in a new tab)

No sign-in needed.

Official repo · GitHub

Reference code, inference scripts and docs from Moonshot AI. The weights themselves download from Hugging Face.

github.com/MoonshotAI/Kimi-Dev (opens in a new tab)

git clone https://github.com/MoonshotAI/Kimi-Dev

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

How it’s rated

Quality 79Great quality (A) · 79 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/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 NVIDIA RTX Spark N1X (6144-core GPU) (128 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.35.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.4.4 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 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 (6144-core GPU) (128 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 40.6 GB 102 GB 8.3 tok/s Slow 56Good quality (B) · 56 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. GGUF (UD-Q2_K_XL) (opens in a new tab)
Q3_K_M 47.1 GB 102 GB 6.5 tok/s Slow 67Good quality (B) · 67 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 (opens in a new tab)
Q4_K_M 55.8 GB 102 GB 5.1 tok/s Slow 76Great quality (A) · 76 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q4_0) (opens in a new tab)
Q5_K_M 63.1 GB 102 GB 4.2 tok/s Slow 77Great quality (A) · 77 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. GGUF (UD-Q5_K_XL) · folder (opens in a new tab)
Q6_K 71.1 GB 102 GB 3.5 tok/s Slow 79Great quality (A) · 79 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 80/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q8_0 88.5 GB 102 GB 2.6 tok/s Very slowtight fit 80Great quality (A) · 80 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
F16 157 GB 102 GB — Won't run 80Great quality (A) · 80 of 100: how capable the model is at F16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (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?