RT-1 TPS calculator
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
818 cards we hold specifications for
Smallest card that fits
Tesla C1080
4 GB · Q8_0 · 1,053 tok/s
Fastest card
B200
96,807 tok/s · 180 GB
Which GPUs can run RT-1?
Set the inputs, read the answer
A longer conversation needs more memory, which can push this model off smaller cards.
Hides cards that would only fit the model by compressing it below this point.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
96,807
tok/s
58,084–154,891 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 0.7 GB | Q8_0 | Comfortable |
|
96,807
tok/s
58,084–154,891 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 0.7 GB | Q8_0 | Comfortable |
|
77,303
tok/s
46,382–123,684 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.7 GB | Q8_0 | Comfortable |
|
77,303
tok/s
46,382–123,684 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.7 GB | Q8_0 | Comfortable |
|
61,823
tok/s
37,094–98,917 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 0.7 GB | Q8_0 | Comfortable |
|
59,173
tok/s
35,504–94,677 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.7 GB | Q8_0 | Comfortable |
|
59,173
tok/s
35,504–94,677 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.7 GB | Q8_0 | Comfortable |
|
56,632
tok/s
33,979–90,611 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 0.7 GB | Q8_0 | Comfortable |
|
50,261
tok/s
30,157–80,417 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 0.7 GB | Q8_0 | Comfortable |
|
50,261
tok/s
30,157–80,417 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.7 GB | Q8_0 | Comfortable |
|
50,261
tok/s
30,157–80,417 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.7 GB | Q8_0 | Comfortable |
|
47,677
tok/s
28,606–76,284 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
40,659
tok/s
24,395–65,054 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
40,659
tok/s
24,395–65,054 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 0.7 GB | Q8_0 | Comfortable |
|
40,659
tok/s
24,395–65,054 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
40,659
tok/s
24,395–65,054 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
40,659
tok/s
24,395–65,054 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 0.7 GB | Q8_0 | Comfortable |
|
30,959
tok/s
18,575–49,534 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.7 GB | Q8_0 | Comfortable |
|
30,959
tok/s
18,575–49,534 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.7 GB | Q8_0 | Comfortable |
|
25,799
tok/s
15,479–41,278 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 0.7 GB | Q8_0 | Comfortable |
|
25,248
tok/s
15,149–40,397 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 0.7 GB | Q8_0 | Comfortable |
|
24,686
tok/s
14,811–39,497 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 0.7 GB | Q8_0 | Comfortable |
|
24,686
tok/s
14,811–39,497 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 0.7 GB | Q8_0 | Comfortable |
|
24,686
tok/s
14,811–39,497 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 0.7 GB | Q8_0 | Comfortable |
|
24,686
tok/s
14,811–39,497 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 0.7 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
- Organisation type
- Industry
- Country
- United States of America
- Published
- 13 December 2022
- Authors
- Anthony Brohan, Noah Brown, Justice Carbajal, Yevgen Chebotar, Joseph Dabis, Chelsea Finn, Keerthana Gopalakrishnan, Karol Hausman, Alex Herzog, Jasmine Hsu, Julian Ibarz, Brian Ichter, Alex Irpan, Tomas Jackson, Sally Jesmonth, Nikhil J Joshi, Ryan Julian, Dmitry Kalashnikov, Yuheng Kuang, Isabel Leal, Kuang-Huei Lee, Sergey Levine, Yao Lu, Utsav Malla, Deeksha Manjunath, Igor Mordatch, Ofir Nach…
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Robotics
- Task
- Robotic manipulation
- Approach
- Reinforcement learning
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
- 35M
- Training data
- tokens
"we also limit the size of the model compared to the original publication, which was 1.2B parameters (resulting in on robot inference time of 1.9s), to be of similar size to RT-1 (37M parameters for Gato vs. 35M for RT-1" 16M params for image tokenizer, 19M for the transformer
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 (unrestricted)
- Training code
- Open source
weights and code here, apache 2.0: https://github.com/google-research/robotics_transformer data here, also apache: https://github.com/google-deepmind/open_x_embodiment
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Why it is tracked
- SOTA improvement
- Record confidence
- Confident
- Citations
- 2,174
I do not see any standard benchmarks that they are claiming SOTA on, only internal evaluations "we evaluate RT-1 with a set of mobile manipulators from Everyday Robots in three environments: two real office kitchens and a training environment modelled off these real kitchens." "Across each category, we find that RT-1 outperforms the prior models significantly. On seen tasks, RT-1 is able to perform 97% of the more than 200 instructions successfully, which is 25% more than BC-Z and 32% more than…
Sources
Where this record came from and when it was last checked.
- Reference
- RT-1: Robotics Transformer for Real-World Control at Scale
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run RT-1
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.
- 01 B300 288 GB · 8,000 GB/s · Q8_0 96,807 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 96,807 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 77,303 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 77,303 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 61,823 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 59,173 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 59,173 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 56,632 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 50,261 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 50,261 tok/s
The smallest GPUs that still run RT-1
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,162 tok/s
- 02 RTX A400 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,162 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,549 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 0.7 GB · Q8_0 · comfortable 2,323 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 0.7 GB · Q8_0 · comfortable 413 tok/s
- 06 Radeon RX 6450M 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,208 tok/s
- 07 Radeon RX 6550M 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,359 tok/s
- 08 Radeon RX 6550S 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,208 tok/s
- 09 Arc A310 4 GB · needs 0.7 GB · Q8_0 · comfortable 975 tok/s
- 10 Arc Pro A30M 4 GB · needs 0.7 GB · Q8_0 · comfortable 1,007 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
0.7 GB
Fastest
96,807 tok/s
RT-1 reaches a parameter count of 35M. That is small enough that hardware is rarely the obstacle, including on cards several years old. The number of cards we track that can run it: 818.
The least hardware that works is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 1,053 tokens per second.
At the other end sits B200, generating roughly 96,807 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
RT-1 was published by Google, in the country recorded as United States of America, during December 2022. The publishing organisation is categorised as industry.
It works in the domain of Robotics, and is recorded as performing the task of robotic manipulation.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.
How fast it runs, and why
Across every card that can run it, the middle of the range sits at 2,718.3 tokens per second. Producing text faster than most people read it: 818 of them.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
What went into building it
Its inclusion criterion: sOTA improvement.
Step by step
How to choose a GPU for RT-1
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
The table lists every card able to hold RT-1, needing around 0.7 GB at a compression of Q8_0. That figure, not the headline performance of a card, is what decides whether it runs.
-
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 RT-1.
-
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 Q8_0 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
Rank by throughput rather than spec sheet
The speed ordering is effectively an ordering by memory bandwidth, for RT-1. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 96,807 tok/s.
-
05
Check the fit verdict before buying
Tight means it loads and works with no room to raise the context later, in the case of RT-1. 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
See what else that card runs
Every card name links to its own page, which runs the same calculation across the whole model catalogue. A card is usually bought for more than one model, so it is worth a look before buying for RT-1.
Answers
RT-1 — common questions
RT-1— 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.
RT-1— can I run it if it does not fit in my GPU?
It can be split between the card and system memory, but it generates painfully slowly that way. Every figure here assumes the whole model is resident on the card.
RT-1— 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: 818. So a second card is rarely the answer here.
RT-1— why does the quantisation differ between cards?
Each card is shown running the least-compressed copy it can hold. The number of distinct compression levels across the cards that fit it: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
RT-1— how accurate are these speed estimates?
Every figure is derived from memory bandwidth and model size, not benchmarked, which is why each is published as a range rather than a single number. One example: 58,084–154,891 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
RT-1— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Tesla C1080, with a memory capacity of 4 GB. It runs the model at a compression of Q8_0 using about 0.7 GB, and produces roughly 1,053 tokens per second. The number of cards able to run it in total: 818.
RT-1— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 96,807 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: 818.
RT-1— how much VRAM does it need?
It needs about 0.7 GB at a compression of Q8_0, 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.
RT-1— can I run it on a GPU holding 8 GB?
Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of Q8_0, using about 0.7 GB and generating roughly 18,030 tokens per second. The fit is comfortable.
RT-1— can I run it on a GPU holding 12 GB?
Yes. The card GeForce RTX 3080 Ti, holding 12 GB, runs it at a compression of Q8_0, using about 0.7 GB and generating roughly 11,041 tokens per second. The fit is comfortable.
RT-1— can I run it on a GPU holding 16 GB?
Yes. The card Tesla V100 SXM2 16 GB, holding 16 GB, runs it at a compression of Q8_0, using about 0.7 GB and generating roughly 13,674 tokens per second. The fit is comfortable.
RT-1— 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 Q8_0, using about 0.7 GB and generating roughly 16,215 tokens per second. The fit is comfortable.
RT-1— 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.
RT-1— how many parameters does it have?
It has a parameter count of 35M. "we also limit the size of the model compared to the original publication, which was 1.2B parameters (resulting in on robot inference time of 1.9s), to be of similar size to RT-1 (37M parameters for Gato vs. 35M for RT-1" 16M params for image tokenizer, 19M for the transformer. 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.
RT-1— who created it?
It was published by Google, based in United States of America, an organisation categorised as industry.
RT-1— when was it released?
It was published in December 2022. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
RT-1— what is it used for?
It works in the domain of Robotics, and is recorded as handling the task of robotic manipulation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
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.