Raises estimated decode speed by about 131%.
~$4,999 MSRP
![]() |
VOOZH | about |
Codestral 22B needs ~23.7 GB VRAM. Mac Studio M2 Ultra 64GB has 46.1 GB. With Q4_K_M quantization, expect ~35 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.2 tok/s
TTFT
5209 ms
Safe context
33K
Memory
23.7 GB / 46.1 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 | 34.6 tok/s | 3054 ms | 33K |
| Coding | B | Runs well | 34.6 tok/s | 5599 ms | 33K |
| Agentic Coding | B | Runs well | 34.6 tok/s | 8145 ms | 33K |
| Reasoning | B | Runs well | 34.6 tok/s | 6617 ms | 33K |
| RAG | B | Runs well | 34.6 tok/s | 10181 ms | 33K |
How Codestral 22B (22B params) fits at each quantization level on Mac Studio M2 Ultra 64GB (46.1 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 8.6 GB | Low | C53 |
Q3_K_S | 3 | 10.8 GB | Low | C53 |
NVFP4 | 4 |
Copy-paste commands to run Codestral 22B on your machine.
Run
ollama run codestralUpgrade options
12.3 GB |
| Medium |
| C54 |
Q4_K_M | 4 | 13.4 GB | Medium | C54 |
Q5_K_M | 5 | 15.8 GB | High | B55 |
Q6_K | 6 | 18.0 GB | High | B56 |
Q8_0Best for your GPU | 8 | 23.5 GB | Very High | B58 |
F16 | 16 | 45.1 GB | Maximum | F0 |
Not always. Mac Studio M2 Ultra 64GB 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.