Raises estimated decode speed by about 166%.
~$10,000 MSRP
![]() |
VOOZH | about |
Codestral 22B needs ~21.9 GB VRAM. MacBook Pro M4 Max 48GB has 34.6 GB. With Q4_K_M quantization, expect ~26 tok/s.
Operating mode
Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.
Current mode
Balanced
Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.
Select quantization to explore
Fit status
Runs well
Decode
37.4 tok/s
TTFT
5174 ms
Safe context
33K
Memory
21.9 GB / 34.6 GB
This setup is broadly balanced for this model.
Shared-memory contention still exists
The OS, browser, and inference runtime all compete for the same physical memory pool, so real-world headroom is less forgiving than raw capacity suggests.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | B | Runs well | 25.6 tok/s | 4120 ms | 33K |
| Coding | B | Runs well | 25.6 tok/s | 7553 ms | 33K |
| Agentic Coding | B | Runs well | 25.6 tok/s | 10986 ms | 33K |
| Reasoning | B | Runs well | 25.6 tok/s | 8926 ms | 33K |
| RAG | B | Runs well | 25.6 tok/s | 13733 ms | 33K |
How Codestral 22B (22B params) fits at each quantization level on MacBook Pro M4 Max 48GB (34.6 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 8.6 GB | Low | C55 |
Q3_K_S | 3 | 10.8 GB | Low | B56 |
NVFP4 | 4 |
Copy-paste commands to run Codestral 22B on your machine.
Run
ollama run codestralUpgrade options
12.3 GB |
| Medium |
| B56 |
Q4_K_M | 4 | 13.4 GB | Medium | B57 |
Q5_K_M | 5 | 15.8 GB | High | B58 |
Q6_K | 6 | 18.0 GB | High | B59 |
Q8_0Best for your GPU | 8 | 23.5 GB | Very High | B59 |
F16 | 16 | 45.1 GB | Maximum | F0 |
Not always. MacBook Pro M4 Max 48GB can often fit larger models thanks to unified memory, but a discrete GPU with dedicated high-bandwidth VRAM may still decode faster once the model fits. For this combination, the important distinction is capacity versus sustained throughput.