Can I run GLM-5.2 on a RTX PRO 6000 Blackwell Max-Q Workstation Edition?
Not at these settings. No indexed quantization of GLM-5.2 fits RTX PRO 6000 Blackwell Max-Q Workstation Edition at any context we compute, with q8_0 KV. The smallest shipped quantization is 169.33 GiB in weights alone, against 89.28 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.7 | 1405.8 | 1406.2 | 1406.9 | 1408.4 | 1411.3 |
| Q8_0 | 746.32 GiB | 747.6 | 747.7 | 748.1 | 748.8 | 750.3 | 753.2 |
| UD-Q6_K | 582.88 GiB | 584.1 | 584.3 | 584.7 | 585.4 | 586.8 | 589.8 |
| UD-Q5_K_M | 522.31 GiB | 523.5 | 523.7 | 524.1 | 524.8 | 526.3 | 529.2 |
| UD-Q5_K_S | 491.05 GiB | 492.3 | 492.5 | 492.8 | 493.6 | 495.0 | 497.9 |
| UD-Q4_K_M | 433.83 GiB | 435.1 | 435.2 | 435.6 | 436.3 | 437.8 | 440.7 |
| UD-Q4_K_S | 406.46 GiB | 407.7 | 407.9 | 408.2 | 409.0 | 410.4 | 413.3 |
| UD-IQ4_NL | 347.07 GiB | 348.3 | 348.5 | 348.8 | 349.6 | 351.0 | 353.9 |
| UD-IQ4_XS | 340.22 GiB | 341.5 | 341.6 | 342.0 | 342.7 | 344.2 | 347.1 |
| UD-Q3_K_M | 319.20 GiB | 320.4 | 320.6 | 321.0 | 321.7 | 323.2 | 326.1 |
| UD-IQ3_S | 287.44 GiB | 288.7 | 288.9 | 289.2 | 289.9 | 291.4 | 294.3 |
| UD-IQ3_XXS | 262.34 GiB | 263.6 | 263.8 | 264.1 | 264.8 | 266.3 | 269.2 |
| UD-IQ2_M | 222.19 GiB | 223.4 | 223.6 | 224.0 | 224.7 | 226.2 | 229.1 |
| UD-IQ2_XXS | 222.08 GiB | 223.3 | 223.5 | 223.9 | 224.6 | 226.0 | 229.0 |
| UD-IQ1_M | 215.35 GiB | 216.6 | 216.8 | 217.1 | 217.9 | 219.3 | 222.2 |
| UD-IQ1_S | 201.83 GiB | 203.1 | 203.2 | 203.6 | 204.3 | 205.8 | 208.7 |
| Q3_K_M | 169.33 GiB | 170.6 | 170.7 | 171.1 | 171.8 | 173.3 | 176.2 |
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.