RDT-1B TPS calculator

Open weights Tsinghua University 1.2B parameters October 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

818 cards that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla C1080

4 GB · Q8_0 · 30.7 tok/s

Fastest card

B200

2,824 tok/s · 180 GB

Which GPUs can run RDT-1B?

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
2,824 tok/s

1,694–4,518 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 2.0 GB Q8_0 Comfortable
2,824 tok/s

1,694–4,518 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 2.0 GB Q8_0 Comfortable
2,255 tok/s

1,353–3,607 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 2.0 GB Q8_0 Comfortable
2,255 tok/s

1,353–3,607 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 2.0 GB Q8_0 Comfortable
1,803 tok/s

1,082–2,885 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 2.0 GB Q8_0 Comfortable
1,726 tok/s

1,036–2,761 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 2.0 GB Q8_0 Comfortable
1,726 tok/s

1,036–2,761 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 2.0 GB Q8_0 Comfortable
1,652 tok/s

991–2,643 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 2.0 GB Q8_0 Comfortable
1,466 tok/s

880–2,346 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 2.0 GB Q8_0 Comfortable
1,466 tok/s

880–2,346 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 2.0 GB Q8_0 Comfortable
1,466 tok/s

880–2,346 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 2.0 GB Q8_0 Comfortable
1,391 tok/s

834–2,225 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 2.0 GB Q8_0 Comfortable
1,186 tok/s

712–1,897 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.0 GB Q8_0 Comfortable
1,186 tok/s

712–1,897 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 2.0 GB Q8_0 Comfortable
1,186 tok/s

712–1,897 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 2.0 GB Q8_0 Comfortable
1,186 tok/s

712–1,897 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.0 GB Q8_0 Comfortable
1,186 tok/s

712–1,897 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 2.0 GB Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 2.0 GB Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 2.0 GB Q8_0 Comfortable
752 tok/s

451–1,204 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 2.0 GB Q8_0 Comfortable
736 tok/s

442–1,178 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 2.0 GB Q8_0 Comfortable
720 tok/s

432–1,152 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 2.0 GB Q8_0 Comfortable
720 tok/s

432–1,152 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 2.0 GB Q8_0 Comfortable
720 tok/s

432–1,152 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 2.0 GB Q8_0 Comfortable
720 tok/s

432–1,152 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 2.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
Tsinghua University
Organisation type
Academia
Country
China
Published
10 October 2024
Authors
Songming Liu, Lingxuan Wu, Bangguo Li, Hengkai Tan, Huayu Chen, Zhengyi Wang, Ke Xu, Hang Su, Jun Zhu

What it does

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

Domain
Robotics
Task
Robotic manipulation
Numerical format
BF16

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
1.2B

Model Training and Inference: "We scale the size of RDT up to 1.2B parameters, establishing it as the currently largest diffusion-based robotic foundation model."

Training data
tokens

Appendix D: "Our pre-training dataset collection includes 46 datasets, with a total scale of 1M+ trajectories and 21TB, making it the largest pre-training collection of robotics datasets to date."

Batch size
1,536

Table 10: Batch size, 32×48

Training compute

The arithmetic performed to train the model, measured in floating-point operations. It is a measure of what the training run cost, not of how fast the finished model answers you.

Training compute
4.1 × 10²² FLOP

Model Training and Inference: "The model is pre-trained on 48 H100 80GB GPUs for a month, giving a total of 1M training iteration steps. It takes three days to fine-tune this model using the same GPUs for 130K steps." Table 10: "Mixed Precision, bf16" Assume 48xGPU, "scheduling reasons" -> NVIDIA H100 SXM5 -> 9.894e14 FLOP/s/GPU Assume 0.3 utilization Assume 1 month + 3 days = 33 days 0.3 * 48 GPU * (33 days) * 9.894e14 FLOP/s/GPU ~= 4.02e22 FLOP

Fine-tuning compute
3.7 × 10²¹ FLOP

Model Training and Inference: "The model is pre-trained on 48 H100 80GB GPUs for a month, giving a total of 1M training iteration steps. It takes three days to fine-tune this model using the same GPUs for 130K steps." Table 10: "Mixed Precision, bf16" Assume 48xGPU, "scheduling reasons" -> NVIDIA H100 SXM5 -> 9.894e14 FLOP/s/GPU Assume 0.3 utilization 3 days = 72 hr = 259200 s 0.3 * 48 GPU * 259200 s * 9.894e14 FLOP/s/GPU ~= 3.69e21 FLOP

The training run

What it physically took to train: which chips, how many, for how long, and what that drew from the wall.

Training hardware
NVIDIA H100 PCIe
Chips used
48
Wall-clock time
720 hours (30 days)

Model Training and Inference: "The model is pre-trained on 48 H100 80GB GPUs for a month, giving a total of 1M training iteration steps. It takes three days to fine-tune this model using the same GPUs for 130K steps."

Power draw
33.1 kW

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

https://huggingface.co/robotics-diffusion-transformer/rdt-1b "All the code, pre-trained model weights, and data are licensed under the MIT license."

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

"Results show that RDT achieves state-of-the-art performance, outperforming baselines by achieving an improvement of 56% in success rates across a wide spectrum of challenging tasks."

Record confidence
Likely
Citations
579

Sources

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

Reference
RDT-1B: a Diffusion Foundation Model for Bimanual Manipulation
Last updated
25 May 2026

The extremes

What the numbers mean

The hardware side

Minimum card

Tesla C1080

Memory needed

2.0 GB

Fastest

2,824 tok/s

RDT-1B reaches a parameter count of 1.2B. 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.

At the low end it is handled by Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 30.7 tokens per second.

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

About this model

RDT-1B was published by Tsinghua University, in the country recorded as China, during October 2024. The category the publisher falls under is academia.

It works in the domain of Robotics, and is recorded as performing the task of robotic manipulation.

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.

How fast it runs, and why

Half the cards that hold it manage more than 79.3 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 799 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.

How it was trained

Training it took a computation budget of roughly 4.1 × 10²² FLOP, on hardware recorded as NVIDIA H100 PCIe. That figure measures what producing the model cost, and has no bearing on how fast it answers.

It is tracked in the underlying dataset for one reason in particular: sOTA improvement.

Step by step

How to choose a GPU for RDT-1B

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

  1. 01

    Read the memory figure first

    Start from what it actually needs, which is the requirement of RDT-1B, needing around 2.0 GB at a compression of Q8_0. That figure, not the headline performance of a card, is what decides whether it runs.

  2. 02

    Match the context to your actual use

    Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason a card that seemed fine stops fitting RDT-1B.

  3. 03

    Decide how much compression you will accept

    Each card runs the least-compressed copy it can hold, 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.

  4. 04

    Rank by throughput rather than spec sheet

    The speed ordering is effectively an ordering by memory bandwidth, for RDT-1B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 2,824 tok/s.

  5. 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 RDT-1B. 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.

  6. 06

    Open the card you have settled on

    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 RDT-1B.

Answers

RDT-1B — common questions

01

RDT-1B— what is it used for?

It works in the domain of Robotics, and is recorded as handling the task of robotic manipulation. These are the areas it was designed around; they describe intent rather than a hard boundary.

02

RDT-1B— 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.

03

RDT-1B— how much compute was used to train it?

Training consumed around 4.1 × 10²² FLOP, on hardware recorded as NVIDIA H100 PCIe. That measures what producing the model cost and says nothing about how quickly it answers once trained — inference speed comes from memory bandwidth, not from the training budget.

04

RDT-1B— 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. Every figure here assumes the whole model is resident on the card.

05

RDT-1B— 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.

06

RDT-1B— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

07

RDT-1B— 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: 1,694–4,518 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

08

RDT-1B— 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 2.0 GB, and produces roughly 30.7 tokens per second. The number of cards able to run it in total: 818.

09

RDT-1B— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 2,824 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: 799.

10

RDT-1B— how much VRAM does it need?

It needs about 2.0 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.

11

RDT-1B— 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 2.0 GB and generating roughly 526 tokens per second. The fit is comfortable.

12

RDT-1B— 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 2.0 GB and generating roughly 322 tokens per second. The fit is comfortable.

13

RDT-1B— 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 2.0 GB and generating roughly 399 tokens per second. The fit is comfortable.

14

RDT-1B— 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 2.0 GB and generating roughly 473 tokens per second. The fit is comfortable.

15

RDT-1B— 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.

16

RDT-1B— how many parameters does it have?

It has a parameter count of 1.2B. Model Training and Inference: "We scale the size of RDT up to 1.2B parameters, establishing it as the currently largest diffusion-based robotic foundation model.". 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.

17

RDT-1B— who created it?

It was published by Tsinghua University, based in China, an organisation categorised as academia.

18

RDT-1B— when was it released?

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

Source

Original publication

Record last updated 25 May 2026

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.