Command R 35B needs ~37.5 GB VRAM. Gaudi 3 128GB has 128.0 GB. With Q4_K_M quantization, expect ~132 tok/s.
Operating mode
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.
Select quantization to explore
Fit status
Runs well
Decode
131.9 tok/s
TTFT
1467 ms
Safe context
131K
Memory
37.5 GB / 128.0 GB
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.
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.
| Workload | Grade | Fit | Decode | TTFT | Context |
|---|---|---|---|---|---|
| Chat | A | Runs well | 131.9 tok/s | 800 ms | 131K |
| Coding | A | Runs well | 131.9 tok/s | 1467 ms | 131K |
| Agentic Coding | A | Runs well | 131.9 tok/s | 2135 ms | 131K |
| Reasoning | A | Runs well | 131.9 tok/s | 1734 ms | 131K |
| RAG | A | Runs well | 131.9 tok/s | 2668 ms | 131K |
How Command R 35B (35B params) fits at each quantization level on Gaudi 3 128GB (128.0 GB usable).
| Quant | Bits | VRAM | Quality | Fit |
|---|---|---|---|---|
Q2_K | 2 | 13.7 GB | Low | B65 |
Q3_K_S | 3 | 17.2 GB | Low | B65 |
NVFP4 | 4 |
Copy-paste commands to run Command R 35B on your machine.
Run
ollama run command-rYour hardware
| Model | Params | Grade | Decode | Capabilities |
|---|---|---|---|---|
| 123B | S | 37.5 tok/s | ||
| 122B | S |
Yes, Gaudi 3 128GB can run Command R 35B with a A grade (Runs well). Expected decode speed: 131.9 tok/s.
Command R 35B (35B parameters) requires approximately 37.5 GB of memory with Q4_K_M quantization.
The recommended quantization for Command R 35B is Q4_K_M, which balances quality and memory efficiency.
On Gaudi 3 128GB, Command R 35B achieves approximately 131.9 tokens per second decode speed with a time-to-first-token of 1467ms using Q4_K_M quantization.
For coding workloads, Command R 35B on Gaudi 3 128GB receives a A grade with 131.9 tok/s and 131K context.
On Gaudi 3 128GB, Command R 35B can safely use up to 131K tokens of context. The model's official context limit is 131K, but available memory constrains the safe maximum.
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.
Paste this snippet into any page to show a live fit card.
<iframe src="https://willitrunai.com/embed/command-r-35b-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:
| Medium |
| B65 |
Q4_K_M | 4 | 21.3 GB | Medium | B66 |
Q5_K_M | 5 | 25.2 GB | High | B66 |
Q6_K | 6 | 28.7 GB | High | B67 |
Q8_0 | 8 | 37.5 GB | Very High | B68 |
F16Best for your GPU | 16 | 71.8 GB | Maximum | A74 |
| 104.1 tok/s |
| 119B | S | 112.9 tok/s |
| 117B | S | 39.5 tok/s |
| 111B | S | 41.8 tok/s |
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.