Command R+ TPS calculator

Open weights Cohere,Cohere for AI 104B parameters April 2024

Each card below is assessed against this model at the context length and minimum quality you choose. Speed is an estimate for a single request, calculated from the card's memory bandwidth and the size of the model once compressed.

Calculated for this model

43 cards that can run it

818 cards we hold specifications for

Smallest card that fits

Radeon Instinct MI200

64 GB · IQ4_XS · 12.8 tok/s

Fastest card

B200

32.6 tok/s · 180 GB

Which GPUs can run Command R+?

Set the inputs, read the answer

Context length tokens

A longer conversation needs more memory, which can push this model off smaller cards.

Minimum quality

Hides cards that would only fit the model by compressing it below this point.

Search cards

Card memory

Also show cards that cannot run it

43 cards match

Calculating

					Needs	Quantisation	Fit
32.6 tok/s 20–52 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	112.0 GB	Q8_0	Comfortable
32.6 tok/s 20–52 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	112.0 GB	Q8_0	Comfortable
31.6 tok/s 19–51 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	63.6 GB	Q4_K_M	Tight
31.6 tok/s 19–51 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	63.6 GB	Q4_K_M	Tight
28.7 tok/s 17–46 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	75.7 GB	Q5_K_M	Tight
26.0 tok/s 16–42 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	112.0 GB	Q8_0	Comfortable
26.0 tok/s 16–42 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	112.0 GB	Q8_0	Comfortable
24.4 tok/s 15–39 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	75.7 GB	Q5_K_M	Tight
24.4 tok/s 15–39 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	75.7 GB	Q5_K_M	Tight
24.4 tok/s 15–39 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	75.7 GB	Q5_K_M	Tight
20.8 tok/s 12–33 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	112.0 GB	Q8_0	Tight
20.2 tok/s 12–32 · low confidence	H100 SXM5 64 GB NVIDIA	64 GB	2,020 GB/s	Mar 2023	57.6 GB	IQ4_XS	Tight
19.9 tok/s 12–32 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	112.0 GB	Q8_0	Tight
19.9 tok/s 12–32 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	112.0 GB	Q8_0	Tight
19.2 tok/s 12–31 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	63.6 GB	Q4_K_M	Tight
19.2 tok/s 12–31 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	63.6 GB	Q4_K_M	Tight
19.2 tok/s 12–31 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	63.6 GB	Q4_K_M	Tight
19.2 tok/s 12–31 · low confidence	H100 CNX NVIDIA	80 GB	2,040 GB/s	Mar 2023	63.6 GB	Q4_K_M	Tight
19.2 tok/s 12–31 · low confidence	H100 PCIe 80 GB NVIDIA	80 GB	2,040 GB/s	Oct 2022	63.6 GB	Q4_K_M	Tight
19.2 tok/s 12–31 · low confidence	H800 PCIe 80 GB NVIDIA	80 GB	2,040 GB/s	Mar 2023	63.6 GB	Q4_K_M	Tight
19.1 tok/s 11–30 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	112.0 GB	Q8_0	Comfortable
18.2 tok/s 11–29 · low confidence	A100 PCIe 80 GB NVIDIA	80 GB	1,940 GB/s	Jun 2021	63.6 GB	Q4_K_M	Tight
18.2 tok/s 11–29 · low confidence	A800 PCIe 80 GB NVIDIA	80 GB	1,940 GB/s	Nov 2022	63.6 GB	Q4_K_M	Tight
16.9 tok/s 10–27 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	112.0 GB	Q8_0	Tight
16.9 tok/s 10–27 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	112.0 GB	Q8_0	Comfortable

Speeds are estimates for a single request — one conversation at a time — calculated from memory bandwidth, model size and quantisation. Real throughput varies with the inference runtime and its version. Figures published by hardware vendors measure many simultaneous requests and are much higher.

On record

Full specification

Everything on record for this model. Most of it describes how it was trained rather than how it runs — useful context for judging how much work went into it, and how it compares with models built at a different scale.

Origin

Who built this model, where, and when it was published.

Organisation: Cohere,Cohere for AI
Organisation type: Industry,Industry
Country: Canada
Published: 4 April 2024

What it does

The problem areas the model was built for. A model can carry several of each.

Domain: Language
Task: Language modeling/generation, Language generation, Translation, Code autocompletion

Size

How large the model is and how much data it was trained on. Parameters are the figure that decides whether it fits on a given graphics card.

Parameters: 104B
Training data: tokens

Availability

Whether you can obtain the model and run it on your own hardware, which is what decides if any of the graphics-card figures on this page apply.

Weights: Open — downloadable
Model access: Open weights (non-commercial)
Training code: Unreleased
Hugging Face: CohereForAI

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Foundation model: Yes
Likely above 10²³ FLOP: Yes
Record confidence: Confident

Sources

Where this record came from and when it was last checked.

Last updated: 28 November 2025

The extremes

The ten fastest GPUs that run Command R+

Ranked by estimated tokens per second, newest card first where speeds tie. Because generation is bound by memory bandwidth, this ordering follows bandwidth rather than any gaming benchmark.

The smallest GPUs that still run Command R+

The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.

What the numbers mean

What it takes to run this model

Minimum card

Radeon Instinct MI200

Memory needed

57.6 GB

Fastest

32.6 tok/s

Command R+ sits at 104B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 43 of the cards we track can hold it.

The smallest card that holds it is the Radeon Instinct MI200 with 64 GB, running it at IQ4_XS and producing around 12.8 tokens per second.

At the other end, a B200 generates roughly 32.6 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.

About this model

Command R+ was published by Cohere,Cohere for AI, in Canada, in April 2024. It comes out of industry,Industry.

It works in Language, and is recorded as doing language modeling/generation, Language generation, Translation, Code autocompletion.

The weights being open is what puts this page in the calculator rather than only in the catalogue: it is a model you can actually hold. It is published under the CohereForAI organisation on Hugging Face.

How fast it runs, and why

Across every card that can run it, the middle of the range is about 18.2 tokens per second, and 37 of them clear the ten tokens per second that roughly matches reading speed.

Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.

Without the attention layout on record, the memory column is an approximation. It is close enough to choose hardware by, and least reliable at long context.

Step by step

How to choose a GPU for Command R+

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

01

Check what it needs before anything else

Look at what Command R+ actually needs — around 57.6 GB at IQ4_XS. No amount of processing power compensates for a card that cannot hold it.
02

Match the context to your actual use

Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Command R+.
03

Decide how much compression you will accept

The quantisation column varies by card, because a bigger card holds a more accurate copy of Command R+ — IQ4_XS on the smallest card that fits. Set a floor to hold the comparison at one level.
04

Rank by throughput rather than spec sheet

Sort by speed to see how cards rank for Command R+. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 32.6 tok/s.
05

Check the fit verdict before buying

A tight fit runs Command R+ but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
06

See what else that card runs

Following a card through to its own page shows every other model it can hold, which is the question that follows once Command R+ is settled.

Answers

Command R+ — common questions

Why does the quantisation differ between cards for Command R+?

Because capacity varies, so does how hard Command R+ has to be squeezed — 4 distinct levels appear in the table above. Set a minimum quality to compare at one.

How accurate are these Command R+ speed estimates?

Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 20–52 tok/s on the B200 rather than a single number.

What GPU do I need to run Command R+?

The smallest card in our catalogue that holds Command R+ is the Radeon Instinct MI200, with 64 GB of memory. It runs the model at IQ4_XS using about 57.6 GB, and produces roughly 12.8 tokens per second. 43 cards in total can run it.

How fast is Command R+ on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 32.6 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 37 of the cards that can run Command R+ clear that.

How much VRAM does Command R+ need?

About 57.6 GB at IQ4_XS compression, which is what the smallest card that runs it uses. Less compression needs more: the figures in the memory column above are recalculated for each card, because each one holds the least-compressed version it can.

Is Command R+ open source?

Its weights are published, so Command R+ can be downloaded and run on your own hardware. Note that open weights is not the same as open source in the full sense — it says nothing about the training data, the training code, or the commercial terms attached.

How many parameters does Command R+ have?

Command R+ has 104B parameters. That figure is the total, and it is what decides how much memory the model needs — roughly half a gigabyte per billion at the compression most people use.

Who created Command R+?

Command R+ was published by Cohere,Cohere for AI, based in Canada, categorised as industry,Industry.

When was Command R+ released?

Command R+ was published in April 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

What is Command R+ used for?

Command R+ works in Language, and is recorded as handling language modeling/generation, Language generation, Translation, Code autocompletion. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

Where can I download Command R+?

Its weights are published under the CohereForAI organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.

Can I run Command R+ if it does not fit in my GPU?

Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down — the nearest miss we calculate is short by 20.4 GB. Our figures for Command R+ assume it is fully resident.

Would two GPUs run Command R+ faster?

A second card roughly doubles the memory available but not the generation rate. With 43 cards already able to run Command R+ alone, the case for pairing is weak.

Source

Original publication

Record last updated 28 November 2025

The other direction

Looking at it from the other side?

This page starts from the model. If you already own a card and want to know everything it will run, start from the hardware instead.

All AI models