Can I run Gemma-4-31B-Fable-5-Agent-Distill on a Apple M3 Pro?
Not at these settings. No indexed quantization of Gemma-4-31B-Fable-5-Agent-Distill fits Apple M3 Pro at any context we compute, with q8_0 KV. The smallest shipped quantization is 12.82 GiB in weights alone, against 12.56 GiB usable. CPU offload can still run it, slowly.
Every quantization at every context
| Quant | Weights● | 4K◐ | 8K◐ | 16K◐ | 32K◐ | 64K◐ | 128K◐ |
|---|---|---|---|---|---|---|---|
| BF16 | 57.20 GiB | 58.8 | 59.1 | 59.8 | 61.1 | 63.8 | 69.1 |
| Q8_0 | 30.39 GiB | 32.0 | 32.3 | 33.0 | 34.3 | 37.0 | 42.3 |
| Q6_K | 23.47 GiB | 25.1 | 25.4 | 26.1 | 27.4 | 30.0 | 35.3 |
| Q5_K_M | 20.35 GiB | 21.9 | 22.3 | 22.9 | 24.3 | 26.9 | 32.2 |
| Q4_K_M | 17.40 GiB | 19.0 | 19.3 | 20.0 | 21.3 | 24.0 | 29.3 |
| IQ4_NL | 16.53 GiB | 18.1 | 18.5 | 19.1 | 20.4 | 23.1 | 28.4 |
| Q3_K_M | 14.24 GiB | 15.8 | 16.2 | 16.8 | 18.1 | 20.8 | 26.1 |
| Q3_K_S | 12.82 GiB | 14.4 | 14.7 | 15.4 | 16.7 | 19.4 | 24.7 |
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, most of this model's layers cache only a 1,024-token window rather than the full context.