Skip to content
localmodel.run

text model · Sarvam · macOS

S Can I run Sarvam-30B on Apple M3 Ultra (256GB)?

Compatibility verdict VRAM threshold engine
Yes, it runsGPU accelerated

Yes. Sarvam-30B runs on Apple M3 Ultra (256GB) at Q4_K_M (~21.7 GB of ~192 GB usable).

Needs ~21.7 GB Device usable ~192 GB

Runs at Q4_K_M using ~21.7 GB of ~192 GB usable. You have room for FP16 for higher quality.

Q4_K_M needed
~21.7 GB
Usable on device
~192 GB
Device memory
256 GB
Best quant
Q4_K_M

Run it

Install commands macOS

Pick your tool. All three load the same Q4_K_M weights.

llama.cpp
$ llama-cli -hf sarvamai/sarvam-30b-gguf:Q4_K_M
LM Studio
$ lms get sarvamai/sarvam-30b-gguf

vLLM is NOT a Mac tool, it is a CUDA/Linux serving engine. Unified memory is not a fixed VRAM slice; ~70% is usable for weights.

How to run it

On macOS use LM Studio (Polished GUI, ships MLX on Apple Silicon, one-click model downloads.). vLLM is NOT a Mac tool, it is a CUDA/Linux serving engine. Unified memory is not a fixed VRAM slice; ~70% is usable for weights.

Model Sarvam
Parameters
30B (MoE, 2.4B active)
Q4_K_M size
19.6 GB
Context
64k
Full Sarvam-30B requirements →
Device macOS
Memory
256 GB unified
Usable for weights
~192 GB
Best runtime
MLX direct / Ollama (MLX backend)
Best models for Apple M3 Ultra (256GB) →

You could also run

Run Sarvam-30B on other hardware

FAQ

Can Apple M3 Ultra (256GB) run Sarvam-30B?

Yes. Sarvam-30B runs on Apple M3 Ultra (256GB) at Q4_K_M (~21.7 GB of ~192 GB usable).

How much memory does Sarvam-30B need?

Apple M3 Ultra (256GB) has room to spare. At Q4_K_M the weights are ~19.6 GB; with KV cache and runtime overhead, budget ~21.7 GB at a 4k context. It is a Mixture-of-Experts model (30B total / 2.4B active), so all experts must stay in memory; memory tracks total params, not active params.

What is the best tool to run Sarvam-30B on macOS?

LM Studio for a simple setup; mlx-lm for the most speed. vLLM is NOT a Mac tool, it is a CUDA/Linux serving engine. Unified memory is not a fixed VRAM slice; ~70% is usable for weights.

Sources

Memory figures are estimates. See methodology.