Can I Run Nemotron 3 Super on Mac Studio (M2 Ultra, 192 GB)?

Written by Jakub Rusinowski · Last updated August 15, 2026

Yes, but it is tight

Yes, but it is tight — Nemotron 3 Super 120B-A12B at Q8_0 needs about 131.2 GB of the 144 GB usable on Mac Studio (M2 Ultra, 192 GB), leaving only ~12.8 GB before the runtime starts swapping. Expect ~28.3 tok/s (estimated), with room for about 32,768 tokens of context.

Confidence: low · Recommended quantization: Q8_0 · Estimated speed: ~28.3 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

Nemotron 3 Super on Mac Studio (M2 Ultra, 192 GB): memory by quantization

Quant	Memory needed	Fits 144 GB?	Max context	Est. speed	Download
F16	243.7 GB	✗ No	—	—	240 GB
Q8_0	131.2 GB	✓ Yes	32K	~28.3 tok/s	127.5 GB
Q6_K	102.1 GB	✓ Yes	64K	~34.9 tok/s	98.4 GB
Q5_K_M	88.7 GB	✓ Yes	128K	~39 tok/s	85.1 GB
Q4_K_M	76.1 GB	✓ Yes	128K	~43.9 tok/s	72.5 GB
Q3_K_M	54.8 GB	✓ Yes	128K	~55.8 tok/s	51.2 GB
Q2_K	43.1 GB	✓ Yes	128K	~65.6 tok/s	39.4 GB

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 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 inferred from the parameter count because this model does not publish its full attention configuration.

FAQ