Can Command R+ 104B run on Gaudi 3 128GB?

YES — Runs Great

A70Great

Estimated from fit model

Command R+ 104B needs ~80.6 GB VRAM. Gaudi 3 128GB has 128.0 GB. With Q4_K_M quantization, expect ~44 tok/s.

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

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) — 80.6 GB, 44.4 tok/s, Runs well

80.6 GB required128.0 GB available

63% VRAM used

Fit status

Runs well

Decode

44.4 tok/s

TTFT

4361 ms

Safe context

131K

Memory

80.6 GB / 128.0 GB

Memory breakdown

Weights63.4 GB

KV Cache3.4 GB

Runtime0.9 GB

Headroom12.8 GB

See how fast it feels

See how fast it feelsCommand R+ 104B on Gaudi 3 128GB
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: 44.4 tok/s decode · 4.4s TTFT (warm) · 111 tok/s prefill

What limits this setup

The raw memory story may look fine, but the software ecosystem is still a constraint here.

Runtime ecosystem is narrower than CUDA

Intel GPUs can look attractive on memory per dollar, but local AI tooling, kernels, and model coverage are still broader and easier on CUDA today.

Best improvement path

Prefer CUDA if you want the path of least resistance

If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.

Performance by workload

Workload	Grade	Fit	Decode	TTFT	Context
Chat	B	Runs well	44.4 tok/s	2378 ms	131K
Coding	A	Runs well	44.4 tok/s	4361 ms	131K
Agentic Coding	A	Runs well	44.4 tok/s	6343 ms	131K
Reasoning	A	Runs well	44.4 tok/s	5153 ms	131K
RAG	A	Runs well	44.4 tok/s	7928 ms	131K

Quantization options

How Command R+ 104B (104B params) fits at each quantization level on Gaudi 3 128GB (128.0 GB usable).

Quant	Bits	VRAM	Quality	Fit
Q2_K	2	40.6 GB	Low	B60
Q3_K_S	3	51.0 GB	Low	B62
NVFP4	4	58.2 GB	Medium	B63
Q4_K_M	4	63.4 GB	Medium	B64
Q5_K_M	5	74.9 GB	High	B65
Q6_KBest for your GPU	6	85.3 GB	High	B65
Q8_0	8	111.3 GB	Very High	F0
F16	16	213.2 GB	Maximum	F0

Get started

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

Run

ollama run command-r-plus

Your hardware

More models your Gaudi 3 128GB can run

Model	Params	Grade	Decode
Devstral 2 123B Instruct	123B	S	37.5 tok/s
Qwen 3.5 122B A10B	122B	S	104.1 tok/s
Mistral Small 4 119B	119B	S	112.9 tok/s
GPT-OSS 120B	117B	S	39.5 tok/s
Command A 111B	111B	S	41.8 tok/s

Frequently asked questions

Can Gaudi 3 128GB run Command R+ 104B?

Yes, Gaudi 3 128GB can run Command R+ 104B with a A grade (Runs well). Expected decode speed: 44.4 tok/s.

How much VRAM does Command R+ 104B need?

Command R+ 104B (104B parameters) requires approximately 80.6 GB of memory with Q4_K_M quantization.

What is the best quantization for Command R+ 104B?

The recommended quantization for Command R+ 104B is Q4_K_M, which balances quality and memory efficiency.

What speed will Command R+ 104B run at on Gaudi 3 128GB?

On Gaudi 3 128GB, Command R+ 104B achieves approximately 44.4 tokens per second decode speed with a time-to-first-token of 4361ms using Q4_K_M quantization.

Can Gaudi 3 128GB run Command R+ 104B for coding?

For coding workloads, Command R+ 104B on Gaudi 3 128GB receives a A grade with 44.4 tok/s and 131K context.

What context window can Command R+ 104B use on Gaudi 3 128GB?

On Gaudi 3 128GB, Command R+ 104B can safely use up to 131K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.

What should I upgrade first if Command R+ 104B feels slow on Gaudi 3 128GB?

Prefer CUDA if you want the path of least resistance. If your goal is maximum runtime coverage, easier troubleshooting, and better support for new local AI releases, CUDA is usually still the safer upgrade path.

Would CUDA be a better path than Gaudi 3 128GB for Command R+ 104B?

Often yes, if your goal is the easiest setup and the widest runtime support. Intel can offer attractive memory capacity, but CUDA still tends to win on tooling maturity, guides, kernels, and model coverage for local AI.

See all results for Gaudi 3 128GB See all hardware for Command R+ 104B

Embed this result▼

Paste this snippet into any page to show a live fit card.

<iframe src="https://willitrunai.com/embed/command-r-plus-104b-on-gaudi-3-128gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: