Can I run DeepSeek-TNG-R1T2-Chimera on a Apple M3 Ultra?
Not at these settings. No indexed quantization of DeepSeek-TNG-R1T2-Chimera fits Apple M3 Ultra at any context we compute, with q4_0 KV. The smallest shipped quantization is 150.08 GiB in weights alone, against 66.96 GiB usable. CPU offload can still run it, slowly.
Every quantization at every context
| Quant | Weights● | 4K◐ | 8K◐ | 16K◐ | 32K◐ | 64K◐ | 128K◐ |
|---|---|---|---|---|---|---|---|
| BF16 | 1250.09 GiB | 1250.8 | 1250.9 | 1251.0 | 1251.3 | 1251.9 | 1253.1 |
| Q8_0 | 664.30 GiB | 665.0 | 665.1 | 665.2 | 665.5 | 666.1 | 667.3 |
| Q6_K | 513.20 GiB | 513.9 | 514.0 | 514.1 | 514.4 | 515.0 | 516.2 |
| Q5_K_M | 443.10 GiB | 443.8 | 443.9 | 444.0 | 444.3 | 444.9 | 446.1 |
| Q5_K_S | 430.46 GiB | 431.2 | 431.2 | 431.4 | 431.7 | 432.3 | 433.5 |
| Q4_1 | 391.52 GiB | 392.2 | 392.3 | 392.4 | 392.7 | 393.4 | 394.6 |
| Q4_K_M | 377.13 GiB | 377.8 | 377.9 | 378.1 | 378.4 | 379.0 | 380.2 |
| Q4_K_S | 354.38 GiB | 355.1 | 355.2 | 355.3 | 355.6 | 356.2 | 357.4 |
| Q4_0 | 353.48 GiB | 354.2 | 354.3 | 354.4 | 354.7 | 355.3 | 356.5 |
| IQ4_NL | 352.58 GiB | 353.3 | 353.4 | 353.5 | 353.8 | 354.4 | 355.6 |
| IQ4_XS | 333.14 GiB | 333.8 | 333.9 | 334.1 | 334.4 | 335.0 | 336.2 |
| Q3_K_M | 297.88 GiB | 298.6 | 298.7 | 298.8 | 299.1 | 299.7 | 300.9 |
| Q3_K_S | 269.83 GiB | 270.5 | 270.6 | 270.8 | 271.1 | 271.7 | 272.9 |
| UD-IQ3_XXS | 254.17 GiB | 254.9 | 255.0 | 255.1 | 255.4 | 256.0 | 257.2 |
| Q2_K_L | 228.17 GiB | 228.9 | 229.0 | 229.1 | 229.4 | 230.0 | 231.2 |
| Q2_K | 227.97 GiB | 228.7 | 228.7 | 228.9 | 229.2 | 229.8 | 231.0 |
| UD-IQ2_M | 212.30 GiB | 213.0 | 213.1 | 213.2 | 213.5 | 214.1 | 215.3 |
| UD-IQ2_XXS | 201.37 GiB | 202.1 | 202.1 | 202.3 | 202.6 | 203.2 | 204.4 |
| UD-IQ1_M | 186.69 GiB | 187.4 | 187.5 | 187.6 | 187.9 | 188.5 | 189.7 |
| UD-IQ1_S | 172.39 GiB | 173.1 | 173.2 | 173.3 | 173.6 | 174.2 | 175.4 |
| UD-TQ1_0 | 150.08 GiB | 150.8 | 150.9 | 151.0 | 151.3 | 151.9 | 153.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.