on

Can the NVIDIA B200 run Command A (111B)?

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

Yes, it runs great

Runs great. At Q8_0 it needs about 128 GB of 180 GB usable, with an estimated speed of 45.0 tok/s.

Best quant
Q8_0
Generation speed
45.0 tok/s
Prompt processing
1,037 tok/s
First token (1K prompt)
1.0 s
Largest safe context
256K

Best app to run it on the NVIDIA B200

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-a-03-2025
  • Ollama One command with Ollama’s own build of this model.
  • LM Studio Point-and-click: search, download and chat in one window.

On Windows

Ollama

Command line + local API · runs on llama.cpp (ggml), MLX (Apple silicon, preview)

  • One command with Ollama’s own build of this model.
  • Serves an OpenAI-compatible API that other apps and coding tools can use.
ollama run command-a:111b-03-2025-q8_0
  • LM Studio Point-and-click: search, download and chat in one window.
  • llama.cpp Usually the first to support new model architectures.

Want an agent? Command A (111B) 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 A (111B)

Recommended for the NVIDIA B200: Q8_0. Every other quantization has its own download link in the table below.

Quickest · Ollama

One command downloads a ready-to-run version and starts a chat.

Get Ollama at ollama.com/download (opens in a new tab) · model page (opens in a new tab)

ollama run command-a:111b-03-2025-q8_0

Quantized files · GGUF

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

Download the Q8_0 files (opens in a new tab)

huggingface.co/unsloth/c4ai-command-a-03-2025-GGUF (opens in a new tab)

ollama run hf.co/unsloth/c4ai-command-a-03-2025-GGUF

Original weights · Hugging Face

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

huggingface.co/CohereLabs/c4ai-command-a-03-2025 (opens in a new tab)

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

How it’s rated

Quality 80Great quality (A) · 80 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking.
How capable the model itself is at Q8_0, 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 B200: 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.36.0 / 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.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 score91.0 / 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 B200

Quant Memory needed Available Speed Runs Quality Download
Q2_K 54.8 GB 180 GB 145 tok/s Runs great 56Good quality (B) · 56 of 100: how capable the model is at Q2_K, whatever it runs on. Match score 72/100 (quality, fit, speed and memory use) sets the ranking. GGUF (opens in a new tab)
Q3_K_M 64.8 GB 180 GB 114 tok/s Runs great 67Good quality (B) · 67 of 100: how capable the model is at Q3_K_M, whatever it runs on. Match score 78/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q4_K_M 78.1 GB 180 GB 88.4 tok/s Runs great 76Great quality (A) · 76 of 100: how capable the model is at Q4_K_M, whatever it runs on. Match score 84/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q5_K_M 89.2 GB 180 GB 73.0 tok/s Runs great 77Great quality (A) · 77 of 100: how capable the model is at Q5_K_M, whatever it runs on. Match score 86/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q6_K 101 GB 180 GB 61.4 tok/s Runs great 79Great quality (A) · 79 of 100: how capable the model is at Q6_K, whatever it runs on. Match score 88/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
Q8_0 128 GB 180 GB 45.0 tok/s Runs great 80Great quality (A) · 80 of 100: how capable the model is at Q8_0, whatever it runs on. Match score 91/100 (quality, fit, speed and memory use) sets the ranking. GGUF · folder (opens in a new tab)
F16 232 GB 180 GB — Won't run 80Great quality (A) · 80 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. GGUF · folder (opens in a new tab) 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?