Only with CPU offload

Qwen3.8-Flash-Next 180B-A6B at Q4_K_M needs 102.0 GB but only 14.4 GB is addressable, so about 87% of the layers would stream from system RAM at roughly 60 GB/s. Expect around 4.6 tokens per second — usable for batch work, painful for chat.

13% on GPU 8K context Q4_K_M · 101.2 GB Qwen Community 1.0 Released 24 Aug 2026 New this week Vision

The open preview of the Qwen4 architecture: a 125B-A6B hybrid (Gated DeltaNet + sparse attention, KV cache on 12 of 48 blocks) plus a 51B n-gram embedding and a 4B draft head — 180B on disk, 6B active. The hosted "Qwen3.8-Flash" is this model with a 1M window.

What hardware do I need for Qwen3.8-Flash-Next 180B-A6B? →

The VRAM budget

weights 101.2 GB
Weights 101.2 GB KV cache @ 8K 0.19 GB Runtime overhead 0.6 GB Over budget 87.6 GB past 14.4 GB

Quantisation ladder

QuantWeightsTotal @ 8KMax contextTok/sQualityFit
Q8_0 178.1 GB 178.9 GB ~2.5 −0.1% ppl 164.5 GB over
Q6_K 137.5 GB 138.3 GB ~3.3 −0.4% ppl 123.9 GB over
Q5_K_M 118.8 GB 119.6 GB ~3.9 −0.8% ppl 105.2 GB over
Q4_K_M 101.2 GB 102.0 GB ~4.6 −1.9% ppl 87.6 GB over
Q3_K_M 81.9 GB 82.7 GB ~5.8 −5.4% ppl 68.3 GB over
Q2_K 70.2 GB 71.0 GB ~7.0 −15% ppl 56.6 GB over

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.8-Flash-Next:Q4_K_M \
    -c 8192 -ngl 6

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

01Download is 101.2 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