Codestral 21B Pruned i1 needs ~18.8 GB VRAM. MacBook Pro M4 Pro 24GB has 17.3 GB. With Q4_K_M quantization, expect ~19 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
1.5 GB over capacity — needs offload or smaller quantization
Fit status
Very compromised (needs ~1 GB host RAM)
Decode
19.2 tok/s
TTFT
10060 ms
Safe context
6K
Memory
18.8 GB / 17.3 GB
Offload
10%
It fits through host-memory offload, and offload is the main reason performance drops.
CPU or host-memory offload is active
About 10% of the working set spills out of accelerator memory, which usually hurts latency and sustained decode throughput.
Very little memory headroom
You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.
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.
Remove offload with more accelerator memory
Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Buy headroom, not only minimum fit
A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.
Increase host RAM if you keep offloading
This setup may need roughly 1.0 GB of extra host RAM just for the offloaded portion, before OS and other tools.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | C | Runs with offload (needs ~0.2 GB host RAM) | 21.4 tok/s | 4933 ms | 6K |
| Coding | D | Very compromised (needs ~1 GB host RAM) | 19.2 tok/s | 10060 ms | 6K |
| Agentic Coding | F | Too heavy | 16.4 tok/s | 17182 ms | 6K |
| Reasoning | D | Very compromised (needs ~1 GB host RAM) | 19.2 tok/s | 11889 ms | 6K |
| RAG | F | Too heavy | 16.4 tok/s | 21477 ms |
How Codestral 21B Pruned i1 (21B params) fits at each quantization level on MacBook Pro M4 Pro 24GB (17.3 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 8.2 GB | Low | C51 |
Q3_K_S | 3 | 10.3 GB | Low | C50 |
NVFP4 | 4 |
Copy-paste commands to run Codestral 21B Pruned i1 on your machine.
Run
lms load hf-mradermacher--codestral-21b-pruned-i1-gguf && lms server startUpgrade options
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Adds memory headroom for longer context windows and future model growth.
~$799 MSRP
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Adds memory headroom for longer context windows and future model growth.
~$1,099 MSRP
Removes host-memory offload, which is usually the single biggest latency and throughput win.
Adds memory headroom for longer context windows and future model growth.
~$1,099 MSRP
RTX 5090 Laptop 24GBBiggest leapRemoves host-memory offload, which is usually the single biggest latency and throughput win.
Raises estimated decode speed by about 206%.
Yes, MacBook Pro M4 Pro 24GB can run Codestral 21B Pruned i1 with a D grade (Very compromised (needs ~1 GB host RAM)). Expected decode speed: 19.2 tok/s.
Codestral 21B Pruned i1 (21B parameters) requires approximately 18.8 GB of memory with Q4_K_M quantization.
The recommended quantization for Codestral 21B Pruned i1 is Q4_K_M, which balances quality and memory efficiency.
On MacBook Pro M4 Pro 24GB, Codestral 21B Pruned i1 achieves approximately 19.2 tokens per second decode speed with a time-to-first-token of 10060ms using Q4_K_M quantization.
For coding workloads, Codestral 21B Pruned i1 on MacBook Pro M4 Pro 24GB receives a D grade with 19.2 tok/s and 6K context.
On MacBook Pro M4 Pro 24GB, Codestral 21B Pruned i1 can safely use up to 6K tokens of context. The model's official context limit is —, but available memory constrains the safe maximum.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/hf-mradermacher--codestral-21b-pruned-i1-gguf-on-m4-pro-24gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview:
| 6K |
11.8 GB |
| Medium |
| C50 |
Q4_K_MBest for your GPU | 4 | 12.8 GB | Medium | C50 |
Q5_K_M | 5 | 15.1 GB | High | F0 |
Q6_K | 6 | 17.2 GB | High | F0 |
Q8_0 | 8 | 22.5 GB | Very High | F0 |
F16 | 16 | 43.1 GB | Maximum | F0 |
Remove offload with more accelerator memory. Prioritize a GPU or unified-memory tier that fits the whole model natively. Removing offload usually helps more than small compute gains.
Not always. MacBook Pro M4 Pro 24GB 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.