text model · Sarvam · Windows
Can I run Sarvam-30B on Nvidia GeForce RTX 4060 Ti (16GB)?
No. Sarvam-30B needs ~21.7 GB even at Q4_K_M, but Nvidia GeForce RTX 4060 Ti (16GB) only has ~15 GB usable.
Needs ~21.7 GB even at Q4_K_M, but only ~15 GB is usable.
That figure is at a 4k context and moves about ±15% as context length changes.
The gap is about 6.7 GB: Sarvam-30B needs roughly 21.7 GB at Q4_K_M and Nvidia GeForce RTX 4060 Ti (16GB) leaves only about 15 GB usable for a model. The lightest tracked hardware that runs Sarvam-30B is the Nvidia GeForce RTX 4090 (24GB) at 24 GB. See Sarvam-30B on Nvidia GeForce RTX 4090 (24GB).
- Q4_K_M needed
- ~21.7 GB
- Usable on device
- ~15 GB
- Device memory
- 16 GB
Which quant fits
How to run it
On Windows use LM Studio (Best GUI on Windows, auto-detects CUDA/Vulkan backends.).
- Parameters
- 30B (MoE, 2.4B active)
- Q4_K_M size
- 19.6 GB
- Context
- 64k
- Memory
- 16 GB vram
- Usable for weights
- ~15 GB
- Power draw
- ~165 W
- Best runtime
- Ollama (CUDA) / llama.cpp CUDA
What you can run instead
Run Sarvam-30B on other hardware
FAQ
Can Nvidia GeForce RTX 4060 Ti (16GB) run Sarvam-30B?
No. Sarvam-30B needs ~21.7 GB even at Q4_K_M, but Nvidia GeForce RTX 4060 Ti (16GB) only has ~15 GB usable.
How much memory does Sarvam-30B need?
Nvidia GeForce RTX 4060 Ti (16GB) does not have enough memory. 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 Windows?
LM Studio for a simple setup; Ollama (CUDA) for the most speed. AMD GPUs run via Vulkan/ROCm at roughly half CUDA throughput. NVIDIA is the smooth path on Windows.
Embed this
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/sarvam-30b/nvidia-rtx-4060-ti-16gb) 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.