text model · Command R · Windows
Can I run Command R 35B on AMD Ryzen AI Halo (128GB)?
Yes. Command R 35B runs on AMD Ryzen AI Halo (128GB) at Q4_K_M (~22.3 GB of ~96 GB usable).
Runs at Q4_K_M using ~22.3 GB of ~96 GB usable. You have room for FP16 for higher quality.
That figure is at a 4k context and moves about ±15% as context length changes. AMD Ryzen AI Halo (128GB) leaves ~73.7 GB of headroom, room to step up to FP16 for higher quality.
- Q4_K_M needed
- ~22.3 GB
- Usable on device
- ~96 GB
- Device memory
- 128 GB
- Best quant
- Q4_K_M
Which quant fits
Running cost · estimate
- Power draw
- ~120 W
- Electricity / 1M tokens
- ~$0.62
At ~$0.15/kWh and the estimated ~8 tok/s, a million generated tokens costs about $0.62 in electricity. TDP is the peak draw, so this is an upper bound. Assumptions.
Run it
Pick your tool. All 3 load the same Q4_K_M weights.
ollama run command-r:35b llama-cli -hf bartowski/c4ai-command-r-v01-GGUF:Q4_K_M lms get bartowski/c4ai-command-r-v01-GGUF - Parameters
- 35B
- Q4_K_M size
- 20.05 GB
- Q8_0 size
- 34.63 GB
- Context
- 128k
- Ollama tag
- command-r:35b
- Memory
- 128 GB unified
- Usable for weights
- ~96 GB
- Power draw
- ~120 W
- Best runtime
- llama.cpp (Vulkan/ROCm) / LM Studio
You could also run
Run Command R 35B on other hardware
FAQ
Can AMD Ryzen AI Halo (128GB) run Command R 35B?
Yes. Command R 35B runs on AMD Ryzen AI Halo (128GB) at Q4_K_M (~22.3 GB of ~96 GB usable).
How much memory does Command R 35B need?
AMD Ryzen AI Halo (128GB) has room to spare. At Q4_K_M the weights are ~20.05 GB; with KV cache and runtime overhead, budget ~22.3 GB at a 4k context.
What is the best tool to run Command R 35B on Windows?
LM Studio for a simple setup; Ollama (CUDA) for the most speed. AMD GPUs run via Vulkan/ROCm at roughly half CUDA throughput. NVIDIA is the smooth path on Windows.
Embed this
A live badge for your model card or README, updated as the data is. [](https://localmodel.run/can-i-run/command-r-35b/amd-ryzen-ai-halo-128gb) Sources
Weights are measured from GGUF files; KV cache and overhead are computed, so totals can vary ~15% with context and runtime. Any tok/s is a bandwidth estimate. See methodology.