Only with CPU offload

Qwen3.5 122B-A10B at Q4_K_M needs 71.1 GB but only 62.4 GB is addressable, so about 12% of the layers would stream from system RAM at roughly 60 GB/s. Expect around 16 tokens per second — usable for batch work, painful for chat.

88% on GPU 8K context Q4_K_M · 70.3 GB Apache 2.0 Released 24 Feb 2026 Vision

The 96–128 GB unified-memory model: 122B of knowledge at 10B-active speed.

What hardware do I need for Qwen3.5 122B-A10B? →

Fits instead: Qwen3.5 9B (6.3 GB) · Qwen3.5 4B (3.5 GB)

The VRAM budget

weights 70.3 GB
Weights 70.3 GB KV cache @ 8K 0.19 GB Runtime overhead 0.6 GB Over budget 8.7 GB past 62.4 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
Q8_0 123.7 GB 124.5 GB ~2.7 −0.1% ppl 62.1 GB over
Q6_K 95.5 GB 96.2 GB ~4.8 −0.4% ppl 33.8 GB over
Q5_K_M 82.5 GB 83.3 GB ~7.5 −0.8% ppl 20.9 GB over
Q4_K_M 70.3 GB 71.1 GB ~16 −1.9% ppl 8.7 GB over
Q3_K_M 56.9 GB 57.7 GB 209K 84 −5.4% ppl Long context
Q2_K 48.7 GB 49.5 GB 256K 98 −15% ppl Long context

Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. Only 12 of its 48 blocks keep a per-token KV cache; the rest are linear-attention, Mamba or convolution blocks with a fixed-size state.

How to run it

terminal
$ llama-server \
    -hf Qwen/Qwen3.5-122B-A10B:Q4_K_M \
    -c 8192 -ngl 42

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

01Download is 70.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