Raises estimated decode speed by about 198%.
~$999 MSRP
![]() |
VOOZH | about |
StarCoder2 15B needs ~16.4 GB VRAM. MacBook Pro M2 Max 32GB has 23.0 GB. With Q5_K_M quantization, expect ~22 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
23.9 tok/s
TTFT
8094 ms
Safe context
16K
Memory
16.4 GB / 23.0 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 | C | Runs well | 21.9 tok/s | 4819 ms | 16K |
| Coding | C | Runs well | 21.9 tok/s | 8836 ms | 16K |
| Agentic Coding | C | Runs well | 21.9 tok/s | 12852 ms | 16K |
| Reasoning | C | Runs well | 21.9 tok/s | 10442 ms | 16K |
| RAG | C | Runs well | 21.9 tok/s | 16065 ms | 16K |
How StarCoder2 15B (15B params) fits at each quantization level on MacBook Pro M2 Max 32GB (23.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 5.9 GB | Low | C48 |
Q3_K_S | 3 | 7.4 GB | Low | C49 |
NVFP4 | 4 |
Copy-paste commands to run StarCoder2 15B on your machine.
Run
docker run --rm -it ghcr.io/ggerganov/llama.cpp:full \
--hf-repo "bigcode/starcoder2-15b" \
--hf-file "starcoder2-15b-Q5_K_M.gguf" \
-c 4096 -ngl 99Upgrade options
8.4 GB |
| Medium |
| C49 |
Q4_K_M | 4 | 9.2 GB | Medium | C50 |
Q5_K_M | 5 | 10.8 GB | High | C51 |
Q6_K | 6 | 12.3 GB | High | C52 |
Q8_0Best for your GPU | 8 | 16.1 GB | Very High | C51 |
F16 | 16 | 30.7 GB | Maximum | F0 |
Not always. MacBook Pro M2 Max 32GB 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.