text model · Sarvam · macOS
Can I run Sarvam-M 24B on Apple M2 (16GB)?
No. Sarvam-M 24B needs ~16.3 GB even at Q4_K_M, but Apple M2 (16GB) only has ~10.5 GB usable.
Needs ~16.3 GB even at Q4_K_M, but only ~10.5 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 5.8 GB: Sarvam-M 24B needs roughly 16.3 GB at Q4_K_M and Apple M2 (16GB) leaves only about 10.5 GB usable for a model. The lightest tracked hardware that runs Sarvam-M 24B is the Nvidia GeForce RTX 4090 (24GB) at 24 GB. See Sarvam-M 24B on Nvidia GeForce RTX 4090 (24GB).
- Q4_K_M needed
- ~16.3 GB
- Usable on device
- ~10.5 GB
- Device memory
- 16 GB
Which quant fits
How to run it
On macOS use LM Studio (Polished GUI, ships MLX on Apple Silicon, one-click model downloads.).
- Parameters
- 24B
- Q4_K_M size
- 14.3 GB
- Q8_0 size
- 25.1 GB
- Context
- 32k
- Memory
- 16 GB unified
- Usable for weights
- ~10.5 GB
- Power draw
- ~50 W
- Best runtime
- Ollama (llama.cpp Metal backend) / MLX
What you can run instead
Run Sarvam-M 24B on other hardware
FAQ
Can Apple M2 (16GB) run Sarvam-M 24B?
No. Sarvam-M 24B needs ~16.3 GB even at Q4_K_M, but Apple M2 (16GB) only has ~10.5 GB usable.
How much memory does Sarvam-M 24B need?
Apple M2 (16GB) does not have enough memory. At Q4_K_M the weights are ~14.3 GB; with KV cache and runtime overhead, budget ~16.3 GB at a 4k context.
What is the best tool to run Sarvam-M 24B 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
[](https://localmodel.run/can-i-run/sarvam-m-24b/apple-m2-16gb) Sources
- apple.com/newsroom/2022/06
- apple.com/newsroom/2022/07
- developer.apple.com
- github.com/ml-explore
- github.com/raullenchai
- huggingface.co/lmstudio-community
- huggingface.co/sarvamai/sarvam-m
- huggingface.co/sarvamai/sarvam-m-q8-gguf
- lmstudio.ai
- stencel.io
- support.apple.com/en-us/103253
- support.apple.com/en-us/111869
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.