Only with CPU offload

DeepSeek-R1-Distill-Qwen 14B at Q4_K_M needs 10.4 GB but only 8.8 GB is addressable, so about 19% of the layers would stream from system RAM at roughly 60 GB/s. Expect around 17 tokens per second — usable for batch work, painful for chat.

81% on GPU 8K context Q4_K_M · 8.3 GB MIT Released Jan 2025

The 2025 reasoning-per-gigabyte pick for a 12 GB card. Qwen3.5 9B in thinking mode has since overtaken it.

What hardware do I need for DeepSeek-R1-Distill-Qwen 14B? →

Fits instead: DeepSeek-R1-Distill-Qwen 7B (5.3 GB)

The VRAM budget

weights 8.3 GB
Weights 8.3 GB KV cache @ 8K 1.50 GB Runtime overhead 0.6 GB Over budget 1.6 GB past 8.8 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
F16 27.6 GB 29.7 GB ~1.7 Reference 20.9 GB over
Q8_0 14.6 GB 16.7 GB ~4.3 −0.1% ppl 7.9 GB over
Q6_K 11.3 GB 13.4 GB ~7.1 −0.4% ppl 4.6 GB over
Q5_K_M 9.8 GB 11.9 GB ~10 −0.8% ppl 3.1 GB over
Q4_K_M 8.3 GB 10.4 GB ~17 −1.9% ppl 1.6 GB over
Q3_K_M 6.7 GB 8.8 GB 7K ~64 −5.4% ppl 0.0 GB over
Q2_K 5.8 GB 7.9 GB 12K 80 −15% ppl Fits

Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it.

How to run it

terminal
$ llama-server \
    -hf deepseek-ai/DeepSeek-R1-Distill-Qwen-14B:Q4_K_M \
    -c 8192 -ngl 38

The engine underneath most of the others. Every knob is exposed. More on llama.cpp.

01Download is 8.3 GB. Keep it on an SSD — a first load off a spinning disk takes minutes.
02Close anything else holding VRAM. A browser with hardware acceleration can sit on 1–2 GB.
03If it falls back to CPU silently, drop the context first, then step down a quantisation.
See all models for this rig Compare with another model