No — not on this device
GLM-5.3-Flash 320B-A18B at Q4_K_M needs 181.2 GB against 25.6 GB usable, and the shortfall of 155.6 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 first natively multimodal GLM-5 and the first hybrid: 34 linear-attention blocks and 11 sparse-attention blocks with a 512-wide latent cache, so a 1M window stays affordable. Z.ai says it beats GLM-5.2 at 18B active; MIT.
What hardware do I need for GLM-5.3-Flash 320B-A18B? →
Fits instead: GLM-4.7-Flash 30B-A3B (18.6 GB)
The VRAM budget
Quantisation ladder
| Quant | Weights | Total @ 8K | Max context | Tok/s | Quality | Fit |
|---|---|---|---|---|---|---|
| Q8_0 | 317.6 GB | 318.3 GB | — | ~0.5 | −0.1% ppl | 292.7 GB over |
| Q6_K | 245.1 GB | 245.8 GB | — | ~0.7 | −0.4% ppl | 220.2 GB over |
| Q5_K_M | 211.9 GB | 212.6 GB | — | ~0.8 | −0.8% ppl | 187.0 GB over |
| Q4_K_M | 180.5 GB | 181.2 GB | — | ~0.9 | −1.9% ppl | 155.6 GB over |
| Q3_K_M | 146.1 GB | 146.8 GB | — | ~1.2 | −5.4% ppl | 121.2 GB over |
| Q2_K | 125.2 GB | 125.9 GB | — | ~1.4 | −15% ppl | 100.3 GB over |
Quality is the published perplexity delta against f16 weights. Max context assumes an f16 KV cache; q8_0 roughly doubles it. Only 11 of its 45 blocks keep a per-token KV cache; the rest are linear-attention, Mamba or convolution blocks with a fixed-size state. This model uses multi-head latent attention, so its cache is a compressed latent rather than full K and V.
How to run it
$ llama-server \
-hf zai-org/GLM-5.3-Flash:Q4_K_M \
-c 8192 -ngl 6
The engine underneath most of the others. Every knob is exposed. More on llama.cpp.