on

Can the NVIDIA RTX PRO 5000 Blackwell 72GB run Sarvam 105B?

71Great quality (A) · 71 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs well (tight fit)

Runs well (tight fit). At Q4_K_M it needs about 69.2 GB of 72.0 GB usable, with an estimated speed of 106 tok/s.

Best quant
Q4_K_M
Generation speed
106 tok/s
Prompt processing
4,680 tok/s
First token (1K prompt)
0.3 s
Largest safe context
82K

Best app to run it on the NVIDIA RTX PRO 5000 Blackwell 72GB

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open Sarvam 105B in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Point-and-click: search, download and chat in one window.

Open Sarvam 105B in LM Studio

  • llama.cpp Usually the first to support new model architectures.
  • Ollama Runs the Hugging Face GGUF with ollama run hf.co/…

How we choose: the files published for this model, your operating system and GPU, whether it fits fully in memory, and published speed tests (MLX vs llama.cpp on Apple silicon, vLLM vs llama.cpp vs Ollama on NVIDIA). Details.

Download Sarvam 105B

Recommended for the NVIDIA RTX PRO 5000 Blackwell 72GB: Q4_K_M. Every other quantization has its own download link in the table below.

Quantized files · GGUF

Works in LM Studio, llama.cpp, Jan and Ollama. No sign-in needed.

Download the Q4_K_M file (opens in a new tab)

huggingface.co/sarvamai/sarvam-105b-gguf (opens in a new tab)

ollama run hf.co/sarvamai/sarvam-105b-gguf:Q4_K_M

Original weights · Hugging Face

Full-precision files from Sarvam AI, for fine-tuning, vLLM, Transformers.

huggingface.co/sarvamai/sarvam-105b (opens in a new tab)

No sign-in needed.

Links checked 3 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 71Great quality (A) · 71 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q4_K_M, from its editorial quality tier scaled by the quantization or precision. It’s the same on any hardware that runs this variant. Scale: A+ 85+ · A 70+ · B 55+ · C 40+ · D under 40.
Runs Runs welltight fit
How well it runs on the NVIDIA RTX PRO 5000 Blackwell 72GB: speed, capped by how well it fits in memory. Runs great: 30+ tokens/s (or near the image, video or decision speed target) · Runs well: 10+ tokens/s · Slow: 3+ tokens/s · Very slow: under 3 · Won’t run: doesn’t fit even with offload. A tight fit or RAM offload caps it at Runs well; heavy offload caps it at Slow.

Match score

To order lists, each result also gets a match score out of 100 from four parts. It favors the most capable model that still runs well.

Model qualityEditorial quality tier of the model, scaled by the quantization or precision used.32.1 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.24.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.15.0 / 15
Memory useRewards using the memory you have, so a bigger, better variant beats a tiny one that leaves most memory idle.15.0 / 15
Match score86.1 / 100

The match score orders results; it is not shown as a grade. Quality and Runs are the two ratings in the tables.

Every quantization on the NVIDIA RTX PRO 5000 Blackwell 72GB

Quant Memory needed Available Speed Runs Quality Download
Q2_K 46.9 GB 72.0 GB 147 tok/s Runs great 52Fair quality (C) · 52 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 56.5 GB 72.0 GB 126 tok/s Runs great 63Good quality (B) · 63 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 69.2 GB 72.0 GB 106 tok/s Runs welltight fit 71Great quality (A) · 71 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking. GGUF · part 1 of 9 (opens in a new tab)
Q5_K_M 79.8 GB 72.0 GB 39.4 tok/s Runs welloffloads to RAM 72Great quality (A) · 72 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 91.4 GB 72.0 GB 20.1 tok/s Runs welloffloads to RAM 74Great quality (A) · 74 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 69/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 117 GB 72.0 GB — Won't run 75Great quality (A) · 75 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 217 GB 72.0 GB — Won't run 75Great quality (A) · 75 of 100: how capable the model is at F16, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. Original weights (opens in a new tab)

Memory figures assume 8K of context. Longer conversations or documents grow the KV cache.

Other hardware that runs it

Quick answers

How much memory does Sarvam 105B need on the NVIDIA RTX PRO 5000 Blackwell 72GB?

At Q4_K_M it needs about 69.2 GB. The NVIDIA RTX PRO 5000 Blackwell 72GB has 72.0 GB usable.

How fast is Sarvam 105B on the NVIDIA RTX PRO 5000 Blackwell 72GB?

About 106 tok/s at Q4_K_M, an estimate from the hardware’s memory bandwidth and the size of the model.

Which quantization of Sarvam 105B should I use on the NVIDIA RTX PRO 5000 Blackwell 72GB?

Q4_K_M. Of the versions that fit, it is the one that runs best; when two run equally well, the check prefers the higher-rated one.

Estimates come from published hardware specs and our open formulas, not from running the model on your machine. Real speed varies with runtime, drivers and settings. Numbers marked “Measured” come from a linked benchmark.

Was this page helpful?