Can I Run Ministral on Mac Studio (M2 Ultra, 192 GB)?

Superseded model. Ministral has been superseded by Mistral Small 4. This page is kept for reference; the newer family is a better starting point. View Mistral Small 4 →

Written by Jakub Rusinowski · Last updated October 16, 2024

Yes — comfortably

Yes, comfortably — Ministral 8B at Q8_0 needs about 10.5 GB of the 144 GB usable on Mac Studio (M2 Ultra, 192 GB), leaving ~133.5 GB spare and running at ~42 tok/s (estimated), with room for about 32,768 tokens of context.

Confidence: high · Recommended quantization: Q8_0 · Estimated speed: ~42 tok/s

Mac Studio (M2 Ultra, 192 GB) — what it gives a model

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

Ministral on Mac Studio (M2 Ultra, 192 GB): memory by quantization

Quant	Memory needed	Fits 144 GB?	Max context	Est. speed	Download
F16	18 GB	✓ Yes	32K	~24.4 tok/s	16 GB
Q8_0	10.5 GB	✓ Yes	32K	~42 tok/s	8.5 GB
Q6_K	8.6 GB	✓ Yes	32K	~51.6 tok/s	6.6 GB
Q5_K_M	7.7 GB	✓ Yes	32K	~57.7 tok/s	5.7 GB
Q4_K_M	6.9 GB	✓ Yes	32K	~64.8 tok/s	4.8 GB
Q3_K_M	5.4 GB	✓ Yes	32K	~82.1 tok/s	3.4 GB
Q2_K	4.6 GB	✓ Yes	32K	~96.2 tok/s	2.6 GB

Which Ministral sizes fit

Variant	Needs at Q4_K_M	Fits?	Est. speed
Ministral 8B	6.9 GB	✓ Fits	~64.8 tok/s
Ministral 3B	3.8 GB	✓ Fits	~111.7 tok/s

What to watch out for

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 M2 Ultra 192 GB limitations

Superseded by the M3 Ultra, which is why it is often the better used buy for large-model work.
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.
192 GB unified memory at 800 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 computed from this model's published attention configuration.

FAQ