Command R TPS calculator

Open weights Cohere,Cohere for AI 35B parameters March 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

132 cards that can run it

818 cards we hold specifications for

Smallest card that fits

RTX A4500

20 GB · Q3_K_M · 20.9 tok/s

Fastest card

B200

96.8 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

132 cards match

Calculating

					Needs	Quantisation	Fit
96.8 tok/s 58–155 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	38.2 GB	Q8_0	Comfortable
96.8 tok/s 58–155 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	38.2 GB	Q8_0	Comfortable
77.3 tok/s 46–124 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	38.2 GB	Q8_0	Comfortable
77.3 tok/s 46–124 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	38.2 GB	Q8_0	Comfortable
61.8 tok/s 37–99 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	38.2 GB	Q8_0	Comfortable
59.2 tok/s 36–95 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	38.2 GB	Q8_0	Comfortable
59.2 tok/s 36–95 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	38.2 GB	Q8_0	Comfortable
56.6 tok/s 34–91 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	38.2 GB	Q8_0	Comfortable
50.3 tok/s 30–80 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	38.2 GB	Q8_0	Comfortable
50.3 tok/s 30–80 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	38.2 GB	Q8_0	Comfortable
50.3 tok/s 30–80 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	38.2 GB	Q8_0	Comfortable
47.7 tok/s 29–76 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	38.2 GB	Q8_0	Comfortable
40.7 tok/s 24–65 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	38.2 GB	Q8_0	Comfortable
40.7 tok/s 24–65 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	38.2 GB	Q8_0	Comfortable
40.7 tok/s 24–65 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	38.2 GB	Q8_0	Comfortable
40.7 tok/s 24–65 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	38.2 GB	Q8_0	Comfortable
40.7 tok/s 24–65 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	38.2 GB	Q8_0	Comfortable
40.4 tok/s 24–65 · low confidence	DRIVE A100 PROD NVIDIA	32 GB	1,870 GB/s	May 2020	25.9 GB	Q5_K_M	Tight
40.4 tok/s 24–65 · low confidence	GRID A100A NVIDIA	32 GB	1,870 GB/s	May 2020	25.9 GB	Q5_K_M	Tight
39.8 tok/s 24–64 · low confidence	GeForce RTX 5090 D V2 NVIDIA	24 GB	1,340 GB/s	Aug 2025	19.8 GB	IQ4_XS	Tight
38.7 tok/s 23–62 · low confidence	GeForce RTX 5090 NVIDIA	32 GB	1,790 GB/s	Jan 2025	25.9 GB	Q5_K_M	Tight
38.7 tok/s 23–62 · low confidence	GeForce RTX 5090 D NVIDIA	32 GB	1,790 GB/s	Jan 2025	25.9 GB	Q5_K_M	Tight
36.3 tok/s 22–58 · low confidence	A30X NVIDIA	24 GB	1,220 GB/s	Apr 2021	19.8 GB	IQ4_XS	Tight
31.0 tok/s 19–50 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	38.2 GB	Q8_0	Comfortable
31.0 tok/s 19–50 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	38.2 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: 11 March 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: 35B
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

How it is classified

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

Foundation model: 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

RTX A4500

Memory needed

17.8 GB

Fastest

96.8 tok/s

Command R reaches a parameter count of 35B. That lands in the range a serious desktop card can handle once the weights are compressed. The number of cards we track that can run it: 132.

The smallest card that holds it is RTX A4500, with a memory capacity of 20 GB, running it at a compression of Q3_K_M and producing around 20.9 tokens per second.

The quickest result comes from B200, generating roughly 96.8 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

About this model

Command R was published by Cohere,Cohere for AI, in the country recorded as Canada, during March 2024. The category the publisher falls under is industry,Industry.

It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Language generation, Translation, Code autocompletion.

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.

How fast it runs, and why

Across every card that can run it, the middle of the range sits at 20.6 tokens per second. Producing text faster than most people read it: 103 of them.

It is a dense model, so every parameter is read for every token produced. That makes speed track memory bandwidth almost exactly — a card with twice the bandwidth generates roughly twice as fast.

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

Read the memory figure first

Start from what it actually needs, which is the requirement of Command R, needing around 17.8 GB at a compression of Q3_K_M. Capacity is the gate — a card either holds it or it does not.
02

Set the context length you will work at

The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect, because at long context a card that handles short questions easily can be dropped by Command R.
03

Choose how far you will compress it

Compression is what makes a model fit smaller cards, at some cost in accuracy, reaching a compression of Q3_K_M on the smallest card that fits. Setting a minimum quality drops the cards that only manage it by squeezing further than you would want, and holds the comparison at one level.
04

Compare tokens per second, not specifications

The speed ordering is effectively an ordering by memory bandwidth, for Command R. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 96.8 tok/s.
05

Look at the headroom, not just the fit

Tight means it loads and works with no room to raise the context later, in the case of Command R. Comfortable means you can grow the context later. That difference matters more than a few tokens per second, so buy for comfortable if you expect to.
06

Open the card you have settled on

Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond Command R.

Answers

Command R — common questions

Command R— what GPU do I need to run it?

The smallest card in our catalogue that holds it is RTX A4500, with a memory capacity of 20 GB. It runs the model at a compression of Q3_K_M using about 17.8 GB, and produces roughly 20.9 tokens per second. The number of cards able to run it in total: 132.

Command R— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 96.8 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and the number of cards clearing that: 103.

Command R— how much VRAM does it need?

It needs about 17.8 GB at a compression of Q3_K_M, 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.

Command R— can I run it on a GPU holding 24 GB?

Yes. The card GeForce RTX 5090 D V2, holding 24 GB, runs it at a compression of IQ4_XS, using about 19.8 GB and generating roughly 39.8 tokens per second. The fit is tight.

Command R— is it open source?

Its weights are published, so it 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.

Command R— how many parameters does it have?

It has a parameter count of 35B. https://huggingface.co/CohereForAI/c4ai-command-r-v01. 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.

Command R— who created it?

It was published by Cohere,Cohere for AI, based in Canada, an organisation categorised as industry,Industry.

Command R— when was it released?

It was published in March 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.

Command R— what is it used for?

It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Language generation, Translation, Code autocompletion. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.

Command R— where can I download it?

The weights are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

Command R— can I run it if it does not fit in my GPU?

Partly. Layers that do not fit sit in system memory and run at a fraction of the speed, so a mostly-offloaded model is rarely worth using. The nearest miss we calculate falls short by 7.5 GB. Every figure here assumes the whole model is resident on the card.

Command R— would two GPUs run it faster?

Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 132. So a second card is rarely the answer here.

Command R— why does the quantisation differ between cards?

A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 6. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

Command R— how accurate are these speed estimates?

They are calculated from specifications rather than measured, and each carries a range. One example: 58–155 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

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