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 is small enough at 1.2B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

At the low end, a Tesla C1080 handles it — 4 GB, at Q8_0, for about 30.7 tokens per second.

The quickest result comes from a B200 at around 2,824 tokens per second — its 8,000 GB/s of bandwidth is what buys that.

About this model

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

It works in Robotics, and is recorded as doing 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, and 799 exceed reading speed outright.

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 roughly 4.1 × 10²² FLOP of computation, on NVIDIA H100 PCIe — a measure of what producing the model cost, not of 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

    Look at what RDT-1B actually needs — around 2.0 GB at Q8_0. No amount of processing power compensates for a card that cannot hold it.

  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 RDT-1B stops fitting a card that seemed fine.

  3. 03

    Decide how much compression you will accept

    Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage RDT-1B by squeezing it further than you would want.

  4. 04

    Rank by throughput rather than spec sheet

    The speed ordering for RDT-1B is effectively an ordering by memory bandwidth, which is why the B200 tops it at 2,824 tok/s.

  5. 05

    Check the fit verdict before buying

    Tight means RDT-1B loads and works, with no room to raise the context later. Comfortable means you can. The difference matters more than a few tokens per second.

  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. Worth a look before buying for RDT-1B alone — a card is usually bought for more than one model.

Answers

RDT-1B — common questions

01

What is RDT-1B used for?

RDT-1B works in Robotics, and is recorded as handling robotic manipulation. These are the areas it was designed around; they describe intent rather than a hard boundary.

02

Where can I download RDT-1B?

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

03

How much compute was used to train RDT-1B?

Around 4.1 × 10²² FLOP, on 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

Can I run RDT-1B 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 RDT-1B is rarely worth using. Every figure here assumes the whole model is on the card.

05

Would two GPUs run RDT-1B faster?

Two cards buy memory rather than speed. That matters for RDT-1B only if one card cannot hold it — 818 can, so a second adds little.

06

Why does the quantisation differ between cards for RDT-1B?

A larger card holds a more accurate copy. Across the cards that run RDT-1B, 1 compression levels are used; the floor control above pins it to one.

07

How accurate are these RDT-1B 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 1,694–4,518 tok/s on the B200 rather than a single number.

08

What GPU do I need to run RDT-1B?

The smallest card in our catalogue that holds RDT-1B is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 2.0 GB, and produces roughly 30.7 tokens per second. 818 cards in total can run it.

09

How fast is RDT-1B on a GPU?

It depends on the card. The quickest we calculate is a 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 799 of the cards that can run RDT-1B clear that.

10

How much VRAM does RDT-1B need?

About 2.0 GB at Q8_0 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.

11

Can I run RDT-1B on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 2.0 GB and generating roughly 526 tokens per second — a comfortable fit.

12

Can I run RDT-1B on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 2.0 GB and generating roughly 322 tokens per second — a comfortable fit.

13

Can I run RDT-1B on a 16 GB GPU?

Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 2.0 GB and generating roughly 399 tokens per second — a comfortable fit.

14

Can I run RDT-1B on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 2.0 GB and generating roughly 473 tokens per second — a comfortable fit.

15

Is RDT-1B open source?

Its weights are published, so RDT-1B 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

How many parameters does RDT-1B have?

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

Who created RDT-1B?

RDT-1B was published by Tsinghua University, based in China, categorised as academia.

18

When was RDT-1B released?

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