Can I Run Devstral on Mac Studio (M3 Ultra, 256 GB)?

Written by Jakub Rusinowski · Last updated September 11, 2026

Yes — comfortably

Yes, comfortably — Devstral-2 123B at Q5_K_M needs about 90.9 GB of the 192 GB usable on Mac Studio (M3 Ultra, 256 GB), leaving ~101.1 GB spare and running at ~5 tok/s (estimated), with room for about 262,144 tokens of context.

Confidence: medium · Recommended quantization: Q5_K_M · Estimated speed: ~5 tok/s

Buy This HardwareRyzen AI Max+ 395 Laptop (Strix Halo, up to 128GB) — 96 GB VRAM · 120 W board power Deploy in the Cloud NowRunPod

or compare on Vast.ai

As an Amazon Associate we earn from qualifying purchases. Cloud GPU links are referral links — we may earn a commission at no extra cost to you.

Mac Studio (M3 Ultra, 256 GB) — what it gives a model

Usable memory for models	192 GB
Memory bandwidth	819 GB/s
Form factor	Desktop
Operating system	macOS
Memory upgradeable	No — soldered

Devstral on Mac Studio (M3 Ultra, 256 GB): memory by quantization

Quant	Memory needed	Fits 192 GB?	Max context	Est. speed	Download
F16	249.7 GB	✗ No	—	—	246 GB
Q8_0	134.4 GB	✓ Yes	128K	~3.4 tok/s	130.7 GB
Q6_K	104.5 GB	✓ Yes	128K	~4.3 tok/s	100.9 GB
Q5_K_M	90.9 GB	✓ Yes	256K	~5 tok/s	87.2 GB
Q4_K_M	77.9 GB	✓ Yes	256K	~5.8 tok/s	74.3 GB
Q3_K_M	56.1 GB	✓ Yes	256K	~8.1 tok/s	52.4 GB
Q2_K	44.1 GB	✓ Yes	256K	~10.4 tok/s	40.4 GB

Which Devstral sizes fit

Variant	Needs at Q4_K_M	Fits?	Est. speed
Devstral-2 123B	77.9 GB	✓ Fits	~5.8 tok/s
Devstral Small 2 24B	17 GB	✓ Fits	~26.9 tok/s
Devstral Small 2505 24B	16.6 GB	✓ Fits	~27.2 tok/s
Devstral-2 22B (Unverified Listing)	15.7 GB	✓ Fits	~29.1 tok/s

What to watch out for

This model does not publish its full attention configuration, so the KV-cache share of these figures is inferred from its parameter count rather than computed exactly.
Memory on this machine is not upgradeable, so the configuration you buy is the ceiling for every model you will ever run on it.

Mac Studio M3 Ultra 256 GB limitations

The largest single-box unified memory pool available, but at roughly half the memory bandwidth of a high-end discrete GPU — very large models load, then run slowly.
Memory is soldered; the configuration chosen at purchase is permanent.

Recommended setup

Ollama or LM Studio (Metal) — MLX for the fastest Apple-native throughput

How these numbers are calculated

Memory need = quantized weights + KV cache at 8,192 tokens (f16) + 0.8 GB runtime overhead.
256 GB unified memory at 819 GB/s, shared between CPU and GPU.
macOS reserves a share of unified memory for the system, so not all of it is available to a model.
Throughput is a memory-bandwidth roofline estimate, not a measurement. It is labelled "estimated" everywhere it appears.
KV cache is inferred from the parameter count because this model does not publish its full attention configuration.

FAQ