on

Can the Intel Xeon W-2100 series NAS (512 GB) run Maple Preview (20B-A1B)?

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

Yes, it runs great

Runs great. At Q4_K_M it needs about 50.7 GB of 471 GB usable, with an estimated speed of 38.3 tok/s.

Best quant
Q4_K_M
Generation speed
38.3 tok/s
Prompt processing
242 tok/s
First token (1K prompt)
4.2 s
Largest safe context
128K

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

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Usually the first to support new model architectures.
llama-server -hf deepgrove/maple-preview-GGUF:Q4_K_M

Want an agent? Maple Preview (20B-A1B) 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 Maple Preview (20B-A1B)

Quantized files · GGUF

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

huggingface.co/deepgrove/maple-preview-GGUF (opens in a new tab)

ollama run hf.co/deepgrove/maple-preview-GGUF

Original weights · Hugging Face

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

huggingface.co/deepgrove/maple-preview (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/deepgrove-ai/llama.cpp (opens in a new tab)

DeepGrove's llama.cpp fork with setup instructions for the Maple GGUF files.

git clone https://github.com/deepgrove-ai/llama.cpp

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

How it’s rated

Quality 66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q4_K_M, 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 Intel Xeon W-2100 series NAS (512 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.9 / 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.14.7 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.2.5 / 15
Match score72.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 Intel Xeon W-2100 series NAS (512 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 46.5 GB 471 GB 58.9 tok/s Runs great 49Fair quality (C) · 49 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 48.3 GB 471 GB 48.0 tok/s Runs great 58Good quality (B) · 58 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 50.7 GB 471 GB 38.3 tok/s Runs great 66Good quality (B) · 66 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q5_K_M 52.7 GB 471 GB 32.2 tok/s Runs great 67Good quality (B) · 67 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 files (opens in a new tab)
Q6_K 55.0 GB 471 GB 27.5 tok/s Runs well 69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 71/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 59.8 GB 471 GB 20.6 tok/s Runs well 70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 70/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 78.8 GB 471 GB 9.9 tok/s Slow 70Great quality (A) · 70 of 100: how capable the model is at F16, whatever it runs on. Match score 67/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?