What GPU do I need to run sarvamai/sarvam-30b?
32.2B parameters, published in F32. View on Hugging Face
sarvam-30b is published by sarvamai on Hugging Face, with 14,683 downloads and 222 likes to date. It's a SarvamMoEForCausalLM model built for text-generation, published natively in F32.
VRAM required & cheapest live GPU fit
Required VRAM = weight size at each precision times a flat 1.2 overhead for activations and fragmentation. The KV-cache grows with context and is not in that factor; it is listed per model below where the architecture is published. Full formula and assumptions: methodology.
| Precision | Weight size | Required VRAM | Cheapest live fit | GPUs needed | Est. $/hr (full fit) |
|---|---|---|---|---|---|
| FP32 | 119.8 GB | 143.7 GB | AMD MI300X | 1 | $2.63/hr |
| cheaper alt. | RTX A5000 | 6 | $1.06/hr | ||
| FP8 (quantized) | 29.9 GB | 35.9 GB | L40 | 1 | $0.759/hr |
| cheaper alt. | RTX 4000 Ada | 2 | $0.440/hr | ||
| INT4 (quantized) | 15.0 GB | 18.0 GB | RTX A5000 | 1 | $0.176/hr |
A GPU is only matched to a row if its hardware supports that precision, and the primary recommendation is always a single-GPU fit when one exists.
INT4 requires a quantized checkpoint actually published for this model, check its Hugging Face page before relying on this row.
Cheapest way to run sarvam-30b at its published (F32) precision: 1× AMD MI300X, at $2.63/hr per GPU ($2.63/hr total). Quantizing to FP8 or INT4 (rows above) can cost less, but requires a compatible quantized checkpoint to exist for this model.
sarvam-30b: KV cache by context length
The KV cache is the memory the attention layers hold for every token of context, on top of the weights. It is not part of the flat 1.2x overhead in the table above, grows with context length and with every concurrent request, and is why a long-context deployment needs more VRAM than the table shows.
Grouped-query attention: every layer caches keys and values for a few shared KV heads. Cached per token: 19,456 bytes at 16-bit.
| Context | KV cache, one sequence |
|---|---|
| 4K | 0.07 GB |
| 32K | 0.59 GB |
| 128K | 2.4 GB |
Computed from the layer, head and window counts in the model's own configuration (sarvamai/sarvam-30b), at 16 bits per cached value. Each concurrent sequence needs its own cache, on top of the weights.
sarvam-30b: common questions
Can sarvam-30b run on a single GPU?
Yes, but not on a desktop card. At FP32 it needs 143.7 GB of VRAM, more than a single 32 GB desktop card holds. The cheapest live single-card fit is a 192.0 GB AMD MI300X at $2.63/hr.
Can sarvam-30b run in 16-bit instead of FP32?
Yes. Its published weights are FP32, 119.8 GB, or 143.7 GB once inference overhead is added. Loading the same weights in 16 bits halves that to 59.9 GB, or 71.9 GB with overhead. How much accuracy the cast costs is model-specific and is not measured here.
What is the least VRAM sarvam-30b can run in?
18.0 GB, at INT4 (quantized), which fits a 24 GB card, against 143.7 GB at FP32. That row assumes an INT4 checkpoint has actually been published for this model, so check its Hugging Face page before planning around it.
Does quantizing sarvam-30b lower the GPU bill?
Yes. At FP32 the cheapest live fit is one AMD MI300X at $2.63/hr. At INT4 (quantized) it drops to one RTX A5000 at $0.176/hr, provided a quantized checkpoint exists for it.
Weight-to-VRAM math, the fit rules, and how live prices are normalized: full methodology.
More sarvamai models
- prism (105.0B, F8_E4M3)
Alternatives at this size
Other models for text-generation within about a third of sarvam-30b's 32.2B parameters, from other model lines.
- Qwen3-32B (32.8B, BF16)
- GLM-4.7-Flash (31.2B, BF16)
- NVIDIA-Nemotron-3-Nano-30B-A3B-BF16 (31.6B, BF16)
- granite-4.1-30b (28.9B, BF16)
- Ornith-1.5-35B-A3B (36.0B, BF16)
More on sarvam-30b
Fits on a 192 GB GPU at FP32: every model that fits in 192 GB.
Fits on a 48 GB GPU at FP8: every model that fits in 48 GB.
Fits on a 24 GB GPU at INT4: every model that fits in 24 GB.
Best chat and assistants models: how sarvam-30b ranks against the rest.
Related reading: AMD MI300X pricing and specs, How much VRAM you need for LLMs, Serving LLMs with vLLM, vLLM vs TensorRT-LLM vs SGLang, and Best GPU for LLM inference.
Your own GPU cloud accounts
One console for the GPU clouds you already rent from. Your keys stay on your machine.
$20 a month, flat