VOOZH about

URL: https://willitrunai.com/can-run/command-r-plus-104b-on-h200-141gb


Can Command R+ 104B run on NVIDIA H200 141GB?

YES — Runs Great

A70Great
Estimated from fit model

Command R+ 104B needs ~81.9 GB VRAM. NVIDIA H200 141GB has 141.0 GB. With Q4_K_M quantization, expect ~64 tok/s.

Runtime: llama.cppCapacity: RoomyBandwidth: HighStack: StandardBottleneck: Balanced
Share:

Operating mode

Choose the run profile you care about

Interactive favors responsiveness, while light API and scale-out lean harder on serving readiness. The fit stays the same, but the recommendation lens changes.

Current mode

Balanced

Balanced for general local use. Keeps the ranking neutral across personal and serving workflows.

Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) — 81.9 GB, 69.1 tok/s, Runs well
81.9 GB required141.0 GB available
58% VRAM used

Fit status

Runs well

Decode

69.1 tok/s

TTFT

2801 ms

Safe context

131K

Memory

81.9 GB / 141.0 GB

Memory breakdown

Weights63.4 GB
KV Cache3.4 GB
Runtime0.9 GB
Headroom14.1 GB

See how fast it feels

See how fast it feelsCommand R+ 104B on NVIDIA H200 141GB
1st promptCold start — includes initialization
>Solve: If a train travels at 60 mph for 2.5 hours, how far does it go?
Let me work through this step by step. Given information: - Speed = 60 mph (miles per hour) - Time = 2.5 hours Formula: Distance = Speed x Time Calculation: Distance = 60 mph x 2.5 h = 150 miles The train travels 150 miles. Double-check: at 60 mph the train covers 60 miles each hour. In half an hour it covers 30 miles. So in 2.5 hours: 60 + 60 + 30 = 150 miles. Confirmed.
2nd promptWarm — model ready, no init overhead
>What if the train stops for 20 minutes halfway?
The stop doesn't change the total distance covered while moving, but it affects total trip time. Breakdown: - First half: 1.25 hours at 60 mph = 75 miles - Stop: 20 minutes (no distance) - Second half: 1.25 hours at 60 mph = 75 miles Total distance: 150 miles (same) Total time: 2.5 h + 0.33 h = 2.83 hours Average speed: 150 / 2.83 = 53 mph The distance stays the same but average speed drops to 53 mph because of the stop.
Estimated: 69.1 tok/s decode · 2.8s TTFT (warm) · 173 tok/s prefill

What limits this setup

This setup is broadly balanced for this model.

No major red flags

This recommendation has enough memory headroom and acceptable estimated speed for the selected workload.

Best improvement path

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatARuns well63.6 tok/s1662 ms131K
CodingARuns well63.6 tok/s3046 ms131K
Agentic CodingARuns well63.6 tok/s4431 ms131K
ReasoningARuns well63.6 tok/s3600 ms131K
RAGARuns well63.6 tok/s5538 ms131K

Quantization options

How Command R+ 104B (104B params) fits at each quantization level on NVIDIA H200 141GB (141.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
40.6 GB
LowB59
Q3_K_S
3
51.0 GB
LowB61
NVFP4
4

Get started

Copy-paste commands to run Command R+ 104B on your machine.

Run

ollama run command-r-plus

Your hardware

More models your NVIDIA H200 141GB can run

ModelParamsGradeDecodeCapabilities
👁 Mistral
Devstral 2 123B Instruct
123BS58.4 tok/s
👁 Alibaba
Qwen 3.5 122B A10B
122BS

Frequently asked questions

See all results for NVIDIA H200 141GBSee all hardware for Command R+ 104B
58.2 GB
Medium
B62
Q4_K_M
4
63.4 GB
MediumB63
Q5_K_M
5
74.9 GB
HighB65
Q6_K
6
85.3 GB
HighB65
Q8_0Best for your GPU
8
111.3 GB
Very HighB65
F16
16
213.2 GB
MaximumF0
162.1 tok/s
👁 Mistral
Mistral Small 4 119B
119BS175.8 tok/s
👁 OpenAI
GPT-OSS 120B
117BS61.4 tok/s
👁 Cohere
Command A 111B
111BS65 tok/s