on

Can the NVIDIA H200 NVL run Command R+ 104B (04-2024)?

63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking.

Yes, it runs great

Runs great. At Q6_K it needs about 94.9 GB of 141 GB usable, with an estimated speed of 39.4 tok/s.

Best quant
Q6_K
Generation speed
39.4 tok/s
Prompt processing
832 tok/s
First token (1K prompt)
1.2 s
Largest safe context
128K

Best app to run it on the NVIDIA H200 NVL

On Linux

vLLM

Inference server · runs on vLLM

  • The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.
vllm serve CohereLabs/c4ai-command-r-plus
  • LM Studio Point-and-click: search, download and chat in one window.
  • SGLang The full model fits in GPU memory at 8-bit, so it can batch many requests: best for serving a team or an app.

On Windows

LM Studio

Desktop app · runs on llama.cpp, MLX

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

Open Command R+ 104B (04-2024) in LM Studio

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

Want an agent? Command R+ 104B (04-2024) supports tool use, so you can pair a llama.cpp or MLX LM server with one of these. Apps that run on this computer come first.

Coding agents

Personal assistants

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 Command R+ 104B (04-2024)

Quantized files · GGUF

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

huggingface.co/bartowski/c4ai-command-r-plus-GGUF (opens in a new tab)

ollama run hf.co/bartowski/c4ai-command-r-plus-GGUF

Original weights · Hugging Face

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

huggingface.co/CohereLabs/c4ai-command-r-plus (opens in a new tab)

Free Hugging Face account needed: accept the license on the model page and the download starts right away.

Links checked 1 day ago against Hugging Face, Ollama and GitHub.

How it’s rated

Quality 63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q6_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 Runs great
How well it runs on the NVIDIA H200 NVL: 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.28.5 / 45
Memory fitFull marks when everything sits in GPU memory; fewer when part spills to system RAM.25.0 / 25
SpeedGeneration speed against a 40 tokens/s target for LLMs, or render time against a target for image and video.14.9 / 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 score83.4 / 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 H200 NVL

Quant Memory needed Available Speed Runs Quality Download
Q2_K 51.3 GB 141 GB 93.2 tok/s Runs great 44Fair quality (C) · 44 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 68/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 60.7 GB 141 GB 73.4 tok/s Runs great 53Fair quality (C) · 53 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 74/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q4_K_M 73.1 GB 141 GB 56.8 tok/s Runs great 60Good quality (B) · 60 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 79/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q5_K_M 83.5 GB 141 GB 46.9 tok/s Runs great 62Good quality (B) · 62 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q6_K 94.9 GB 141 GB 39.4 tok/s Runs great 63Good quality (B) · 63 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 83/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
Q8_0 120 GB 141 GB 28.9 tok/s Runs well 64Good quality (B) · 64 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 81/100 (quality, fit, speed and memory use) sets the ranking. GGUF files (opens in a new tab)
F16 217 GB 141 GB — Won't run 64Good quality (B) · 64 of 100: how capable the model is at F16, whatever it runs on. Match score 8/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?