on

Can the Intel Arc B570 run Maple Preview (20B-A1B)?

49Fair quality (C) · 49 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well (tight fit)

Runs well (tight fit). At Q2_K it needs about 9.3 GB of 10.0 GB usable, with an estimated speed of 176 tok/s.

Best quant
Q2_K
Generation speed
176 tok/s
Prompt processing
8,490 tok/s
First token (1K prompt)
0.3 s
Largest safe context
55K

Best app to run it on the Intel Arc B570

On Windows

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf deepgrove/maple-preview-GGUF:Q2_K
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

On Linux

llama.cpp

Command line + local API · runs on llama.cpp

  • Supports Intel Arc through SYCL and Vulkan.
  • Usually the first to support new model architectures.
llama-server -hf deepgrove/maple-preview-GGUF:Q2_K
  • LM Studio Point-and-click: search, download and chat in one window.
  • Jan Point-and-click: search, download and chat in one window.

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, 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 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 49Fair quality (C) · 49 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 76/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 Runs welltight fit
How well it runs on the Intel Arc B570: 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.22.1 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.24.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.15.0 / 15
Match score76.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 Arc B570

Quant Memory needed Available Speed Runs Quality Download
Q2_K 9.3 GB 10.0 GB 176 tok/s Runs welltight fit 49Fair quality (C) · 49 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 11.1 GB 10.0 GB 130 tok/s Runs welloffloads to RAM 58Good quality (B) · 58 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 66/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 13.5 GB 10.0 GB 86.4 tok/s Runs welloffloads to RAM 66Good quality (B) · 66 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 files (opens in a new tab)
Q5_K_M 15.6 GB 10.0 GB 66.0 tok/s Slowheavy RAM offload 67Good quality (B) · 67 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 17.8 GB 10.0 GB 52.3 tok/s Slowheavy RAM offload 69Good quality (B) · 69 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 65/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 22.6 GB 10.0 GB 35.4 tok/s Slowheavy RAM offload 70Great quality (A) · 70 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 64/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 41.6 GB 10.0 GB — Won't run 70Great quality (A) · 70 of 100: how capable the model is at F16, whatever it runs on. Match score 9/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?