Can Command R+ 104B run on NVIDIA L40S 48GB?

YES — With Q2_K

B63Good
Estimated from fit model

Command R+ 104B needs ~49.7 GB VRAM. NVIDIA L40S 48GB has 48.0 GB. With Q2_K quantization, expect ~6 tok/s.

Runtime: llama.cppCapacity: OffloadBandwidth: HighStack: StandardBottleneck: Memory bandwidth
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.

Command R+ 104B at Q4_K_M needs 72.6 GB — too much for NVIDIA L40S 48GB (48.0 GB). Runs at Q2_K (49.7 GB) with low quality.
Capabilities:

Select quantization to explore

Q4_K_M (Medium quality) 72.6 GB, exceeds 48.0 GB available
72.6 GB required48.0 GB available
151% VRAM needed

24.6 GB over capacity — needs offload or smaller quantization

Fit status

Too heavy

Decode

2.1 tok/s

TTFT

92571 ms

Safe context

4K

Memory

72.6 GB / 48.0 GB

Offload

30%

Memory breakdown

Weights63.4 GB
KV Cache3.4 GB
Runtime0.9 GB
Headroom4.8 GB

See how fast it feels

With memory offload — actual speed may be lower
See how fast it feelsCommand R+ 104B on NVIDIA L40S 48GB
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: 2.1 tok/s decode · 92.6s TTFT (warm) · 5 tok/s prefill

What limits this setup

This model fits, but memory bandwidth is the part holding decode speed back.

Throughput will feel slow

Estimated decode speed is only 6.2 tok/s, so this is more of a technical fit than a comfortable daily-driver setup.

Very little memory headroom

You can run the model, but there is not much room left for longer context, bigger batches, extra apps, or future model updates.

Best improvement path

Prioritize bandwidth, not only capacity

If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.

Buy headroom, not only minimum fit

A slightly larger memory tier gives you safer context growth and makes the recommendation more future-proof.

Performance by workload

WorkloadGradeFitDecodeTTFTContext
ChatFToo heavy3.5 tok/s30081 ms4K
CodingFToo heavy3.3 tok/s57987 ms4K
Agentic CodingFToo heavy3.0 tok/s92926 ms4K
ReasoningFToo heavy3.3 tok/s68530 ms4K
RAGFToo heavy3.0 tok/s116157 ms4K

Quantization options

How Command R+ 104B (104B params) fits at each quantization level on NVIDIA L40S 48GB (48.0 GB usable).

QuantBitsVRAMQualityFit
Q2_K
2
40.6 GB
LowF0
Q3_K_S
3
51.0 GB
LowF0
NVFP4
4
58.2 GB
MediumF0
Q4_K_M
4
63.4 GB
MediumF0
Q5_K_M
5
74.9 GB
HighF0
Q6_K
6
85.3 GB
HighF0
Q8_0
8
111.3 GB
Very HighF0
F16
16
213.2 GB
MaximumF0

Get started

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

Run

ollama run command-r-plus

アップグレードオプション

Command R+ 104Bを快適に動かすハードウェア

Frequently asked questions

Can NVIDIA L40S 48GB run Command R+ 104B?

Yes, NVIDIA L40S 48GB can run Command R+ 104B at Q2_K quantization (Runs with offload (needs ~1.4 GB host RAM)). The recommended Q4_K_M requires 72.6 GB which exceeds available memory, but at Q2_K it needs only 49.7 GB. Expected decode speed: 6.2 tok/s.

How much VRAM does Command R+ 104B need?

Command R+ 104B (104B parameters) requires approximately 72.6 GB at Q4_K_M quantization. On NVIDIA L40S 48GB, it fits at Q2_K using 49.7 GB.

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

The recommended quantization is Q4_K_M, but on NVIDIA L40S 48GB the best fitting quantization is Q2_K, which uses 49.7 GB.

What speed will Command R+ 104B run at on NVIDIA L40S 48GB?

On NVIDIA L40S 48GB, Command R+ 104B achieves approximately 6.2 tokens per second decode speed with a time-to-first-token of 31367ms using Q2_K quantization.

Can NVIDIA L40S 48GB run Command R+ 104B for coding?

For coding workloads, Command R+ 104B on NVIDIA L40S 48GB receives a F grade with 3.3 tok/s and 4K context.

What context window can Command R+ 104B use on NVIDIA L40S 48GB?

On NVIDIA L40S 48GB, Command R+ 104B can safely use up to 8K tokens of context at Q2_K quantization. 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 NVIDIA L40S 48GB?

Prioritize bandwidth, not only capacity. If this workload feels slow, the next useful step is often a GPU tier with materially faster memory bandwidth rather than only a small bump in capacity.

See all results for NVIDIA L40S 48GBSee 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-l40s-48gb" width="400" height="180" frameborder="0" style="border:none;border-radius:12px;overflow:hidden;" title="Will It Run AI — fit result"></iframe>

Preview: