Can Devstral Small 1.1 run on MacBook Pro M3 Pro 36GB?
YES — Tight Fit
Devstral Small 1.1 needs ~21.9 GB VRAM. MacBook Pro M3 Pro 36GB has 25.9 GB. With Q4_K_M quantization, expect ~8 tok/s.
Operating mode
Choose the run profile you care about
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
Tight fit
Decode
8.0 tok/s
TTFT
24078 ms
Safe context
43K
Memory
21.9 GB / 25.9 GB
Memory breakdown
See how fast it feels
What limits this setup
The model fits in shared memory, but shared-memory bandwidth is now the real limiter.
Fit does not mean dedicated-VRAM speed
Unified or shared memory can make a model technically fit, but sustained tokens per second may still trail a discrete high-bandwidth GPU with less total memory.
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.
Best improvement path
Prioritize bandwidth, not only capacity
If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Performance by workload
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | S | Runs well | 8.0 tok/s | 13134 ms | 43K |
| Coding | S | Tight fit | 7.5 tok/s | 25884 ms | 43K |
| Agentic Coding | S | Tight fit | 8.0 tok/s | 35023 ms | 43K |
| Reasoning | S | Tight fit | 8.0 tok/s | 28456 ms | 43K |
| RAG | S | Tight fit | 8.0 tok/s | 43779 ms | 43K |
Quantization options
How Devstral Small 1.1 (24B params) fits at each quantization level on MacBook Pro M3 Pro 36GB (25.9 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 9.4 GB | Low | S87 |
Q3_K_S | 3 | 11.8 GB | Low | S89 |
NVFP4 | 4 | 13.4 GB | Medium | S90 |
Q4_K_M | 4 | 14.6 GB | Medium | S89 |
Q5_K_M | 5 | 17.3 GB | High | S89 |
Q6_KBest for your GPU | 6 | 19.7 GB | High | S89 |
Q8_0 | 8 | 25.7 GB | Very High | F0 |
F16 | 16 | 49.2 GB | Maximum | F0 |
Get started
Copy-paste commands to run Devstral Small 1.1 on your machine.
Run
lms load Devstral-Small-2507 && lms server startYour hardware
More models your MacBook Pro M3 Pro 36GB can run
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 30.5B | S | 16.6 tok/s | ||
| 27B | S | 7.2 tok/s | ||
| 27B | S | 5.5 tok/s | ||
| 35B | A | 12.1 tok/s | ||
| 30B | S | 17.1 tok/s |
Frequently asked questions
Can MacBook Pro M3 Pro 36GB run Devstral Small 1.1?
Yes, MacBook Pro M3 Pro 36GB can run Devstral Small 1.1 with a S grade (Tight fit). Expected decode speed: 7.5 tok/s.
How much VRAM does Devstral Small 1.1 need?
Devstral Small 1.1 (24B parameters) requires approximately 21.9 GB of memory with Q4_K_M quantization.
What is the best quantization for Devstral Small 1.1?
The recommended quantization for Devstral Small 1.1 is Q4_K_M, which balances quality and memory efficiency.
What speed will Devstral Small 1.1 run at on MacBook Pro M3 Pro 36GB?
On MacBook Pro M3 Pro 36GB, Devstral Small 1.1 achieves approximately 7.5 tokens per second decode speed with a time-to-first-token of 25884ms using Q4_K_M quantization.
Can MacBook Pro M3 Pro 36GB run Devstral Small 1.1 for coding?
For coding workloads, Devstral Small 1.1 on MacBook Pro M3 Pro 36GB receives a S grade with 7.5 tok/s and 43K context.
What context window can Devstral Small 1.1 use on MacBook Pro M3 Pro 36GB?
On MacBook Pro M3 Pro 36GB, Devstral Small 1.1 can safely use up to 43K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.
What should I upgrade first if Devstral Small 1.1 feels slow on MacBook Pro M3 Pro 36GB?
Prioritize bandwidth, not only capacity. If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.
Is unified memory on MacBook Pro M3 Pro 36GB as fast as VRAM for Devstral Small 1.1?
Not always. MacBook Pro M3 Pro 36GB 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.
Embed this result▼
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/devstral-small-2507-on-m3-pro-36gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>
Preview: