on

Can the NVIDIA GeForce RTX 5090 run Sarvam 105B?

52Fair quality (C) · 52 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking.

Yes, but slowly (heavy RAM offload)

Slow (heavy RAM offload). At Q2_K it needs about 44.9 GB of 32.0 GB usable, with an estimated speed of 36.1 tok/s.

Best quant
Q2_K
Generation speed
36.1 tok/s
Prompt processing
5,937 tok/s
First token (1K prompt)
0.3 s
Largest safe context
—

Best app to run it on the NVIDIA GeForce RTX 5090

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Splits the model between GPU memory and system RAM, which this setup needs.
  • Point-and-click: search, download and chat in one window.

Open Sarvam 105B in LM Studio

  • llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.
  • Ollama Splits the model between GPU memory and system RAM, which this setup needs.

On Linux

LM Studio

Desktop app · runs on llama.cpp, MLX

  • Splits the model between GPU memory and system RAM, which this setup needs.
  • Point-and-click: search, download and chat in one window.

Open Sarvam 105B in LM Studio

  • llama.cpp Splits the model between GPU memory and system RAM, which this setup needs.
  • Ollama Splits the model between GPU memory and system RAM, which this setup needs.

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

Quantized files · GGUF

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

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

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

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 2 days ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 52Fair quality (C) · 52 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q2_K, 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 Slowheavy RAM offload
How well it runs on the NVIDIA GeForce RTX 5090: 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.23.6 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.4.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.14.2 / 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 score56.9 / 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 GeForce RTX 5090

Quant Memory needed Available Speed Runs Quality Download
Q2_K 44.9 GB 32.0 GB 36.1 tok/s Slowheavy RAM offload 52Fair quality (C) · 52 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 56/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q3_K_M 54.5 GB 32.0 GB — Won't run 63Good quality (B) · 63 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 8/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q4_K_M 67.2 GB 32.0 GB — Won't run 71Great quality (A) · 71 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF · part 1 of 9 (opens in a new tab)
Q5_K_M 77.8 GB 32.0 GB — Won't run 72Great quality (A) · 72 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 9/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q6_K 89.4 GB 32.0 GB — Won't run 74Great quality (A) · 74 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 10/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 115 GB 32.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 215 GB 32.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

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?