Can I run GLM-5.2 on a Radeon RX 6500 XT?
Not at these settings. No indexed quantization of GLM-5.2 fits Radeon RX 6500 XT at any context we compute, with q8_0 KV. The smallest shipped quantization is 169.33 GiB in weights alone, against 3.72 GiB usable. CPU offload can still run it, slowly.
Every quantization at every context
| Quant | Weights● | 4K◐ | 8K◐ | 16K◐ | 32K◐ | 64K◐ | 128K◐ |
|---|---|---|---|---|---|---|---|
| BF16 | 1404.42 GiB | 1405.6 | 1405.7 | 1406.1 | 1406.8 | 1408.3 | 1411.2 |
| Q8_0 | 746.32 GiB | 747.5 | 747.6 | 748.0 | 748.7 | 750.2 | 753.1 |
| UD-Q6_K | 582.88 GiB | 584.0 | 584.2 | 584.6 | 585.3 | 586.7 | 589.7 |
| UD-Q5_K_M | 522.31 GiB | 523.4 | 523.6 | 524.0 | 524.7 | 526.2 | 529.1 |
| UD-Q5_K_S | 491.05 GiB | 492.2 | 492.4 | 492.7 | 493.5 | 494.9 | 497.8 |
| UD-Q4_K_M | 433.83 GiB | 435.0 | 435.1 | 435.5 | 436.2 | 437.7 | 440.6 |
| UD-Q4_K_S | 406.46 GiB | 407.6 | 407.8 | 408.1 | 408.9 | 410.3 | 413.2 |
| UD-IQ4_NL | 347.07 GiB | 348.2 | 348.4 | 348.7 | 349.5 | 350.9 | 353.8 |
| UD-IQ4_XS | 340.22 GiB | 341.4 | 341.5 | 341.9 | 342.6 | 344.1 | 347.0 |
| UD-Q3_K_M | 319.20 GiB | 320.3 | 320.5 | 320.9 | 321.6 | 323.1 | 326.0 |
| UD-IQ3_S | 287.44 GiB | 288.6 | 288.8 | 289.1 | 289.8 | 291.3 | 294.2 |
| UD-IQ3_XXS | 262.34 GiB | 263.5 | 263.7 | 264.0 | 264.7 | 266.2 | 269.1 |
| UD-IQ2_M | 222.19 GiB | 223.3 | 223.5 | 223.9 | 224.6 | 226.1 | 229.0 |
| UD-IQ2_XXS | 222.08 GiB | 223.2 | 223.4 | 223.8 | 224.5 | 225.9 | 228.9 |
| UD-IQ1_M | 215.35 GiB | 216.5 | 216.7 | 217.0 | 217.8 | 219.2 | 222.1 |
| UD-IQ1_S | 201.83 GiB | 203.0 | 203.1 | 203.5 | 204.2 | 205.7 | 208.6 |
| Q3_K_M | 169.33 GiB | 170.5 | 170.6 | 171.0 | 171.7 | 173.2 | 176.1 |
Figures are GiB of total memory: weights plus KV cache plus compute buffer and backend overhead. Weights and KV are near-exact; the overhead term is modeled. Hover any cell for the breakdown.
Why other calculators disagree
A parameters × bits ÷ 8 estimate ignores two things that dominate at long context. First, the weights themselves are not the nominal rate — quantizations are mixtures, so the real file is consistently larger than the label implies. Second, this model uses latent attention and allocates no V cache at all, so any formula reading num_key_value_heads overstates its cache by more than an order of magnitude.