No — not on this device

DeepSeek-R1 671B at Q4_K_M needs 378.4 GB against 51.2 GB usable, and the shortfall of 327.2 GB is more than 256 GB of system RAM can cover at a tolerable speed. A smaller sibling or a lower quantisation is the honest answer here.

Does not fit 8K context Q4_K_M · 377.3 GB MIT Released Jan 2025

The January 2025 moment. Multi-head latent attention keeps its KV cache tiny; the weights do not.

What hardware do I need for DeepSeek-R1 671B? →

Fits instead: DeepSeek-R1-Distill-Llama 70B (42.8 GB) · DeepSeek-R1-Distill-Qwen 32B (21.0 GB)

The VRAM budget

weights 377.3 GB
Weights 377.3 GB KV cache @ 8K 0.54 GB Runtime overhead 0.6 GB Over budget 327.2 GB past 51.2 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
Q8_0 664.0 GB 665.1 GB ~0.5 −0.1% ppl 613.9 GB over
Q6_K 512.4 GB 513.6 GB ~0.6 −0.4% ppl 462.4 GB over
Q5_K_M 442.9 GB 444.0 GB ~0.7 −0.8% ppl 392.8 GB over
Q4_K_M 377.3 GB 378.4 GB ~0.8 −1.9% ppl 327.2 GB over
Q3_K_M 305.4 GB 306.6 GB ~1.0 −5.4% ppl 255.4 GB over
Q2_K 261.7 GB 262.8 GB ~1.2 −15% ppl 211.6 GB over

Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. This model uses multi-head latent attention, so its cache is a compressed latent rather than full K and V.

How to run it

terminal
$ llama-server \
    -hf deepseek-ai/DeepSeek-R1:Q4_K_M \
    -c 8192 -ngl 8

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

01Download is 377.3 GB. Keep it on an SSD — a first load off a spinning disk takes minutes.
02With no GPU, thread count matters more than clock. Start at one thread per physical core.
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