on

Can the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (16 GB) run Kimi Dev 72B?

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

No, it doesn’t fit

No. Kimi Dev 72B needs about 33.3 GB even at Q2_K; the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (16 GB) has 12.0 GB usable.

Download Kimi Dev 72B

Recommended: Q2_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 Q2_K (UD-Q2_K_XL) file (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:UD-Q2_K_XL

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 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 56Good quality (B) · 56 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_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 Won't run
How well it runs on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (16 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.7.6 / 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.0.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.0.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.0.0 / 15
Match score7.6 / 100

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

It doesn’t fit, so only a reduced share of the quality points counts and fit, speed and memory use score zero.

Every quantization on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (16 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 33.3 GB 12.0 GB — Won't run 56Good quality (B) · 56 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 7/100 (quality, fit, speed and memory use) sets the ranking. GGUF (UD-Q2_K_XL) (opens in a new tab)
Q3_K_M 39.9 GB 12.0 GB — Won't run 67Good quality (B) · 67 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 48.6 GB 12.0 GB — Won't run 76Great quality (A) · 76 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q4_0) (opens in a new tab)
Q5_K_M 55.9 GB 12.0 GB — Won't run 77Great quality (A) · 77 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. GGUF (UD-Q5_K_XL) · folder (opens in a new tab)
Q6_K 63.9 GB 12.0 GB — Won't run 79Great quality (A) · 79 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q8_0 81.3 GB 12.0 GB — Won't run 80Great quality (A) · 80 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
F16 150 GB 12.0 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.

Hardware that can run it

Models that do run on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS (16 GB)

Quick answers

How much memory does Kimi Dev 72B need on the Intel Celeron J3455 / N3450 (Apollo Lake) NAS 16GB?

Even at Q2_K it needs about 33.3 GB; the Intel Celeron J3455 / N3450 (Apollo Lake) NAS 16GB has 12.0 GB usable.

What can the Intel Celeron J3455 / N3450 (Apollo Lake) NAS 16GB run instead?

K2 Horizon 7B, Gemma 4 12B and MiMo V2.6 Distill Qwen 9B run best on it; the page lists more, each with its speed.

What hardware can run Kimi Dev 72B?

NVIDIA RTX PRO 6000 Blackwell 96GB, M4 Max 64GB and M2 Ultra 192GB run it; the page lists more, each with its speed.

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?