Yes — Command R+ 2 (104B) runs at 24 tok/s on M4 Max with 128 GB RAM using Q4_K_M quantization via MLX. First token latency is 1.4s. A capable open-source LLM with 104B parameters.
LLMCheck measured Command R+ 2 on M4 Max using the standard methodology: Q4_K_M quantization, 256-token input, 512-token output, 3 runs averaged on a freshly-booted system.
| Metric | Value |
|---|---|
| Tokens per second | 24 tok/s |
| Time to first token | 1.4s |
| Quantization | Q4_K_M |
| Minimum RAM | 128 GB |
| Recommended engine | MLX |
| Parameters | 104B |
| Benchmark date | 2026-07 |
Q4_K_M 104B MLX M4 Max
The recommended engine for Command R+ 2 on M4 Max is MLX. Install with pip and pull the model:
Alternatively, you can use Ollama for a simpler setup:
| Chip | Speed | First Token | Min RAM | Engine |
|---|---|---|---|---|
| M5 Max | 30 tok/s | 1.0s | 128 GB | MLX |
| M5 Max | 28 tok/s | 1.2s | 64 GB | Ollama |
To run Command R+ 2 on M4 Max you need:
Command R+ 2 needs about 128 GB of unified memory. These current Apple Silicon Macs have the headroom to run it comfortably:
Not sure which Mac fits your budget? See the best Mac for running this →
As an Amazon Associate, LLMCheck earns from qualifying purchases. These affiliate links cost you nothing extra and help keep our benchmarks free.
See how Command R+ 2 stacks up against other models on your specific Mac hardware.
Open Compare Tool Full Leaderboard