on

Can the Intel Core Ultra 200V (Arc 140V) (32 GB) run DeepSeek Coder V2 Lite (16B)?

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

Yes, it runs great

Runs great. At Q5_K_M it needs about 13.5 GB of 18.2 GB usable, with an estimated speed of 38.2 tok/s.

Best quant
Q5_K_M
Generation speed
38.2 tok/s
Prompt processing
1,833 tok/s
First token (1K prompt)
0.6 s
Largest safe context
157K

Best app to run it on the Intel Core Ultra 200V (Arc 140V) (32 GB)

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 lmstudio-community/DeepSeek-Coder-V2-Lite-Instruct-GGUF:Q5_K_M
  • 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 lmstudio-community/DeepSeek-Coder-V2-Lite-Instruct-GGUF:Q5_K_M
  • 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 V2 Lite (16B) 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 V2 Lite (16B)

Recommended for the Intel Core Ultra 200V (Arc 140V) (32 GB): Q5_K_M. 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-v2:16b-lite-instruct-q5_K_M

Quantized files · GGUF

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

Download the Q5_K_M file (opens in a new tab)

huggingface.co/lmstudio-community/DeepSeek-Coder-V2-Lite-Instruct-GGUF (opens in a new tab)

ollama run hf.co/lmstudio-community/DeepSeek-Coder-V2-Lite-Instruct-GGUF:Q5_K_M

Original weights · Hugging Face

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

huggingface.co/deepseek-ai/DeepSeek-Coder-V2-Lite-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-V2 (opens in a new tab)

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

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 50Fair quality (C) · 50 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q5_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 Core Ultra 200V (Arc 140V) (32 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.22.7 / 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.14.7 / 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 score77.4 / 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 Core Ultra 200V (Arc 140V) (32 GB)

Quant Memory needed Available Speed Runs Quality Download
Q2_K 8.6 GB 18.2 GB 68.8 tok/s Runs great 36Basic quality (D) · 36 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 67/100 (quality, fit, speed and memory use) sets the ranking.
Q3_K_M 10.0 GB 18.2 GB 56.4 tok/s Runs great 43Fair quality (C) · 43 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF (Q3_K_L) (opens in a new tab)
Q4_K_M 11.9 GB 18.2 GB 45.2 tok/s Runs great 49Fair quality (C) · 49 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 (opens in a new tab)
Q5_K_M 13.5 GB 18.2 GB 38.2 tok/s Runs great 50Fair quality (C) · 50 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 77/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q6_K 15.2 GB 18.2 GB 32.6 tok/s Runs great 51Fair quality (C) · 51 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 76/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q8_0 19.0 GB 18.2 GB 20.9 tok/s Runs wellover GPU memory limit 52Fair quality (C) · 52 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 59/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
F16 33.7 GB 18.2 GB — Won't run 52Fair quality (C) · 52 of 100: how capable the model is at F16, whatever it runs on. Match score 7/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

Quick answers

How much memory does DeepSeek Coder V2 Lite (16B) need on the Intel Core Ultra 200V (Arc 140V) 32GB?

At Q5_K_M it needs about 13.5 GB. The Intel Core Ultra 200V (Arc 140V) 32GB has 18.2 GB usable.

How fast is DeepSeek Coder V2 Lite (16B) on the Intel Core Ultra 200V (Arc 140V) 32GB?

About 38.2 tok/s at Q5_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of DeepSeek Coder V2 Lite (16B) should I use on the Intel Core Ultra 200V (Arc 140V) 32GB?

Q5_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

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?