text model · Sarvam · macOS
Can I run Sarvam-105B on Apple M3 Ultra (256GB)?
Yes. Sarvam-105B runs on Apple M3 Ultra (256GB) at Q4_K_M (~67.5 GB of ~192 GB usable).
Runs at Q4_K_M using ~67.5 GB of ~192 GB usable. You have room for Q8_0 for higher quality.
That figure is at a 4k context and moves about ±15% as context length changes. Apple M3 Ultra (256GB) leaves ~124.5 GB of headroom, room to step up to Q8_0 for higher quality.
- Q4_K_M needed
- ~67.5 GB
- Usable on device
- ~192 GB
- Device memory
- 256 GB
- Best quant
- Q4_K_M
Which quant fits
Run it
Pick your tool. All 2 load the same Q4_K_M weights.
llama-cli -hf sarvamai/sarvam-105b-gguf:Q4_K_M lms get sarvamai/sarvam-105b-gguf How to run it
On macOS use LM Studio (Polished GUI, ships MLX on Apple Silicon, one-click model downloads.).
- Parameters
- 105B (MoE, 10.3B active)
- Q4_K_M size
- 64.2 GB
- Context
- 128k
- Memory
- 256 GB unified
- Usable for weights
- ~192 GB
- Power draw
- ~270 W
- Best runtime
- MLX direct / Ollama (MLX backend)
You could also run
Run Sarvam-105B on other hardware
FAQ
Can Apple M3 Ultra (256GB) run Sarvam-105B?
Yes. Sarvam-105B runs on Apple M3 Ultra (256GB) at Q4_K_M (~67.5 GB of ~192 GB usable).
How much memory does Sarvam-105B need?
Apple M3 Ultra (256GB) has room to spare. At Q4_K_M the weights are ~64.2 GB; with KV cache and runtime overhead, budget ~67.5 GB at a 4k context. It is a Mixture-of-Experts model (105B total / 10.3B active), so all experts must stay in memory; memory tracks total params, not active params.
What is the best tool to run Sarvam-105B 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.
Embed this
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/sarvam-105b/apple-m3-ultra-256gb) Sources
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.