on

Can the Intel Arc A580 run DeepSeek Coder 6.7B Instruct?

23Basic quality (D) · 23 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.

Yes, it runs well (tight fit)

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

Best quant
Q2_K
Generation speed
117 tok/s
Prompt processing
2,007 tok/s
First token (1K prompt)
0.5 s
Largest safe context
8K

Best app to run it on the Intel Arc A580

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 TheBloke/deepseek-coder-6.7B-instruct-GGUF:Q2_K
  • LM Studio Point-and-click: search, download and chat in one window.
  • Ollama Intel GPU support here is experimental (Vulkan).

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 TheBloke/deepseek-coder-6.7B-instruct-GGUF:Q2_K
  • LM Studio Point-and-click: search, download and chat in one window.
  • Ollama Intel GPU support here is experimental (Vulkan).

Want an agent? DeepSeek Coder 6.7B Instruct 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 DeepSeek Coder 6.7B Instruct

Recommended for the Intel Arc A580: Q2_K. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run deepseek-coder:6.7b-instruct-q2_K

Quantized files · GGUF

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

Download the Q2_K file (opens in a new tab)

huggingface.co/TheBloke/deepseek-coder-6.7B-instruct-GGUF (opens in a new tab)

ollama run hf.co/TheBloke/deepseek-coder-6.7B-instruct-GGUF:Q2_K

Original weights · Hugging Face

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

huggingface.co/deepseek-ai/deepseek-coder-6.7b-instruct (opens in a new tab)

No sign-in needed.

Official repo · GitHub

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

github.com/deepseek-ai/DeepSeek-Coder (opens in a new tab)

git clone https://github.com/deepseek-ai/DeepSeek-Coder

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

How it’s rated

Quality 23Basic quality (D) · 23 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.
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 A580: 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.10.7 / 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 score64.7 / 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 A580

Quant Memory needed Available Speed Runs Quality Download
Q2_K 8.0 GB 8.0 GB 117 tok/s Runs welltight fit 23Basic quality (D) · 23 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 (opens in a new tab)
Q3_K_M 8.6 GB 8.0 GB 49.0 tok/s Runs welloffloads to RAM 28Basic quality (D) · 28 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 52/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q4_K_M 9.4 GB 8.0 GB 26.7 tok/s Slowheavy RAM offload 32Basic quality (D) · 32 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 45/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q5_K_M 10.1 GB 8.0 GB 18.9 tok/s Slowheavy RAM offload 32Basic quality (D) · 32 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 44/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 10.8 GB 8.0 GB 14.2 tok/s Slowheavy RAM offload 33Basic quality (D) · 33 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 43/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 12.4 GB 8.0 GB 9.0 tok/s Slowheavy RAM offload 34Basic quality (D) · 34 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 41/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 18.8 GB 8.0 GB — Won't run 34Basic quality (D) · 34 of 100: how capable the model is at F16, whatever it runs on. Match score 4/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?