VOOZH about

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


Can Command R+ 104B run on NVIDIA H20 96GB?

YES — Runs Great

A72Great
Estimated from fit model

Command R+ 104B needs ~77.4 GB VRAM. NVIDIA H20 96GB has 96.0 GB. With Q4_K_M quantization, expect ~51 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) — 77.4 GB, 55.5 tok/s, Runs well
77.4 GB required96.0 GB available
81% VRAM used

Fit status

Runs well

Decode

55.5 tok/s

TTFT

3486 ms

Safe context

103K

Memory

77.4 GB / 96.0 GB

Memory breakdown

Weights63.4 GB
KV Cache3.4 GB
Runtime0.9 GB
Headroom9.6 GB

See how fast it feels

See how fast it feelsCommand R+ 104B on NVIDIA H20 96GB
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: 55.5 tok/s decode · 3.5s TTFT (warm) · 139 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 well51.1 tok/s2068 ms103K
CodingARuns well51.1 tok/s3791 ms103K
Agentic CodingBTight fit51.1 tok/s5514 ms103K
ReasoningARuns well51.1 tok/s4480 ms103K
RAGBTight fit51.1 tok/s6892 ms103K

Quantization options

How Command R+ 104B (104B params) fits at each quantization level on NVIDIA H20 96GB (96.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
40.6 GB
LowB63
Q3_K_S
3
51.0 GB
LowB65
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 H20 96GB can run

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

Frequently asked questions

See all results for NVIDIA H20 96GBSee all hardware for Command R+ 104B
58.2 GB
Medium
B65
Q4_K_M
4
63.4 GB
MediumB65
Q5_K_MBest for your GPU
5
74.9 GB
HighB65
Q6_K
6
85.3 GB
HighF0
Q8_0
8
111.3 GB
Very HighF0
F16
16
213.2 GB
MaximumF0
130.3 tok/s
👁 Mistral
Mistral Small 4 119B
119BS141.2 tok/s
👁 OpenAI
GPT-OSS 120B
117BS49.4 tok/s
👁 Cohere
Command A 111B
111BS52.2 tok/s