No — not on this device
Qwen3.8-Flash-Next 180B-A6B at Q4_K_M needs 102.0 GB against 25.6 GB usable, and the shortfall of 76.4 GB is more than 32 GB of system RAM can cover at a tolerable speed. A smaller sibling or a lower quantisation is the honest answer here.
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? →
Fits instead: Qwen3.8 27B (16.7 GB)
The VRAM budget
Quantisation ladder
| Quant | Weights | Total @ 8K | Max context | Tok/s | Quality | Fit |
|---|---|---|---|---|---|---|
| Q8_0 | 178.1 GB | 178.9 GB | — | ~1.6 | −0.1% ppl | 153.3 GB over |
| Q6_K | 137.5 GB | 138.3 GB | — | ~2.1 | −0.4% ppl | 112.7 GB over |
| Q5_K_M | 118.8 GB | 119.6 GB | — | ~2.4 | −0.8% ppl | 94.0 GB over |
| Q4_K_M | 101.2 GB | 102.0 GB | — | ~2.8 | −1.9% ppl | 76.4 GB over |
| Q3_K_M | 81.9 GB | 82.7 GB | — | ~3.5 | −5.4% ppl | 57.1 GB over |
| Q2_K | 70.2 GB | 71.0 GB | — | ~4.1 | −15% ppl | 45.4 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
$ llama-server \
-hf Qwen/Qwen3.8-Flash-Next:Q4_K_M \
-c 8192 -ngl 11
The engine underneath most of the others. Every knob is exposed. More on llama.cpp.