Can I Run Qwen 3 on 8 GB system RAM?

作者： Jakub Rusinowski · 最后更新： 2025年4月28日

Yes

Yes — Qwen 3 8B at Q3_K_M needs about 5.5 GB of the 6.4 GB usable on 8 GB system RAM (~0.9 GB spare), at ~15.8 tok/s (estimated), with room for about 8,192 tokens of context.

Confidence: high · Recommended quantization: Q3_K_M · Estimated speed: ~15.8 tok/s

Buy This HardwareIntel Arc B570 10GB — 10 GB VRAM · 150 W board power Deploy in the Cloud NowRTX 4090 on RunPod — from $0.34/hr · rate checked 2026-07

or compare on Vast.ai from $0.35/hr (typical low · varies)

As an Amazon Associate we earn from qualifying purchases. Cloud GPU links are referral links — we may earn a commission at no extra cost to you.

8 GB system RAM — what it gives a model

Usable memory for models	6.4 GB
Memory bandwidth	90 GB/s

Qwen 3 on 8 GB system RAM: memory by quantization

Quant	Memory needed	Fits 6.4 GB?	Max context	Est. speed	Download
F16	18.4 GB	✗ No	—	—	16.4 GB
Q8_0	10.7 GB	✗ No	—	—	8.7 GB
Q6_K	8.7 GB	✗ No	—	—	6.7 GB
Q5_K_M	7.8 GB	✗ No	—	—	5.8 GB
Q4_K_M	7 GB	✗ No	—	—	5 GB
Q3_K_M	5.5 GB	✓ Yes	8K	~15.8 tok/s	3.5 GB
Q2_K	4.7 GB	✓ Yes	16K	~19.5 tok/s	2.7 GB

Which Qwen 3 sizes fit

Variant	Needs at Q4_K_M	Fits?	Est. speed
Qwen 3 235B-A22B (MoE)	144.3 GB	✗ Too large	—
Qwen 3 32B	22.8 GB	✗ Too large	—
Qwen 3 30B-A3B (MoE)	20 GB	✗ Too large	—
Qwen 3 14B	11.1 GB	✗ Too large	—
Qwen 3 8B	7 GB	✗ Too large	—

What to watch out for

Only ~0.9 GB of headroom at Q3_K_M: a longer context or a second application can push this into swapping.
Q3_K_M is the only quantization that fits, and it is a heavily degraded one — expect noticeably worse output than the same model at Q4_K_M. A smaller model at Q4 is usually the better trade.
5 larger variants of Qwen 3 do not fit and would need CPU offload or different hardware.
These figures assume CPU-only inference. Any discrete GPU, even an 8 GB one, will be several times faster for models that fit in its VRAM.

Recommended setup

llama.cpp (CPU build) or Ollama — both run without a GPU

How these numbers are calculated

Memory need = quantized weights + KV cache at 8,192 tokens (f16) + 0.8 GB runtime overhead.
6.4 GB of the 8 GB is treated as usable for model weights (80% — the rest is the OS and running applications).
DDR5-5600 dual channel at 89.6 GB/s peak. CPU decode is assumed to sustain 35% of that peak, because CPU inference is not purely bandwidth-bound — it also spends real time in compute and thread synchronisation. This figure is an assumption, not a fitted constant: no CPU measurement is in the calibration set.
CPU-only inference: no GPU is assumed. A GPU of any size will beat these figures substantially.
Throughput is a memory-bandwidth roofline estimate, not a measurement. It is labelled "estimated" everywhere it appears.
KV cache is computed from this model's published attention configuration.

FAQ