DETR TPS calculator

Open weights Facebook 60M parameters May 2020

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 · 614 tok/s

Fastest card

B200

56,471 tok/s · 180 GB

Which GPUs can run DETR?

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
56,471 tok/s

33,882–90,353 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 0.8 GB Q8_0 Comfortable
56,471 tok/s

33,882–90,353 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 0.8 GB Q8_0 Comfortable
45,093 tok/s

27,056–72,149 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 0.8 GB Q8_0 Comfortable
45,093 tok/s

27,056–72,149 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 0.8 GB Q8_0 Comfortable
36,064 tok/s

21,638–57,702 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 0.8 GB Q8_0 Comfortable
34,518 tok/s

20,711–55,228 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 0.8 GB Q8_0 Comfortable
34,518 tok/s

20,711–55,228 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 0.8 GB Q8_0 Comfortable
33,035 tok/s

19,821–52,856 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 0.8 GB Q8_0 Comfortable
29,319 tok/s

17,591–46,910 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 0.8 GB Q8_0 Comfortable
29,319 tok/s

17,591–46,910 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 0.8 GB Q8_0 Comfortable
29,319 tok/s

17,591–46,910 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 0.8 GB Q8_0 Comfortable
27,812 tok/s

16,687–44,499 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 0.8 GB Q8_0 Comfortable
23,718 tok/s

14,231–37,948 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 0.8 GB Q8_0 Comfortable
23,718 tok/s

14,231–37,948 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 0.8 GB Q8_0 Comfortable
23,718 tok/s

14,231–37,948 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 0.8 GB Q8_0 Comfortable
23,718 tok/s

14,231–37,948 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 0.8 GB Q8_0 Comfortable
23,718 tok/s

14,231–37,948 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 0.8 GB Q8_0 Comfortable
18,059 tok/s

10,836–28,895 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 0.8 GB Q8_0 Comfortable
18,059 tok/s

10,836–28,895 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 0.8 GB Q8_0 Comfortable
15,049 tok/s

9,030–24,079 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 0.8 GB Q8_0 Comfortable
14,728 tok/s

8,837–23,565 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 0.8 GB Q8_0 Comfortable
14,400 tok/s

8,640–23,040 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 0.8 GB Q8_0 Comfortable
14,400 tok/s

8,640–23,040 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 0.8 GB Q8_0 Comfortable
14,400 tok/s

8,640–23,040 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 0.8 GB Q8_0 Comfortable
14,400 tok/s

8,640–23,040 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 0.8 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
Facebook
Organisation type
Industry
Country
United States of America
Published
26 May 2020
Authors
Nicolas Carion, Francisco Massa, Gabriel Synnaeve, Nicolas Usunier, Alexander Kirillov, Sergey Zagoruyko

What it does

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

Domain
Vision
Task
Object detection
Approach
Supervised

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
60M

60M per Table 1

Training data
826,000 tokens
Epochs
500
Batch size
64

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 × 10²⁰ FLOP

"Training the baseline model for 300 epochs on 16 V100 GPUs takes 3 days, with 4 images per GPU (hence a total batch size of 64). For the longer schedule used to compare with Faster R-CNN we train for 500 epochs with learning rate drop after 400 epochs. This schedule adds 1.5 AP compared to the shorter schedule." 48 V100-days for baseline DETR model. Larger model had 1.5x the params and 5/3 as many epochs, so required ~2.5x as much training compute. 125 teraflop/s * 2.5 * 48 * 24 * 3600 * 0.3 …

How it was established
Hardware

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 V100
Compute cost
$960

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

Apache 2.0: https://github.com/facebookresearch/detr

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
Highly cited
Record confidence
Confident
Citations
18,148

Sources

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

Reference
End-to-End Object Detection with Transformers
Last updated
25 May 2026

The extremes

What the numbers mean

What you need to run it

Minimum card

Tesla C1080

Memory needed

0.8 GB

Fastest

56,471 tok/s

DETR is small enough at 60M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

The least hardware that works is a Tesla C1080. Its 4 GB is enough at Q8_0 compression, giving roughly 614 tokens per second.

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

About this model

DETR was published by Facebook, in United States of America, in May 2020. The organisation is categorised as industry.

It works in Vision, and is recorded as doing object detection.

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 1,585.7 tokens per second, and 818 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.

Training and provenance

The training run consumed about 4 × 10²⁰ FLOP, on NVIDIA V100. That figure describes the cost of creating it and has no bearing on how quickly it generates text.

It was trained on about 826,000 tokens of text.

Its inclusion criterion is highly cited.

Step by step

How to choose a GPU for DETR

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

  1. 01

    Check what it needs before anything else

    Look at what DETR actually needs — around 0.8 GB at Q8_0. No amount of processing power compensates for a card that cannot hold it.

  2. 02

    Decide how long your conversations run

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

  3. 03

    Choose how far you will compress it

    Compression is what makes DETR fit smaller cards, at some cost in accuracy — Q8_0 on the smallest card that fits. A minimum quality removes the ones that go too far.

  4. 04

    Rank by throughput rather than spec sheet

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

  5. 05

    Read the fit column last

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

  6. 06

    Check the card from the other side

    Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond DETR.

Answers

DETR — common questions

01

Can I run DETR on a 16 GB GPU?

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

02

Can I run DETR on a 24 GB GPU?

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

03

Is DETR open source?

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

04

How many parameters does DETR have?

DETR has 60M parameters. 60M per Table 1. 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.

05

Who created DETR?

DETR was published by Facebook, based in United States of America, categorised as industry.

06

When was DETR released?

DETR was published in May 2020. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

07

What is DETR used for?

DETR works in Vision, and is recorded as handling object detection. These are the areas it was designed around; they describe intent rather than a hard boundary.

08

Where can I download DETR?

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

09

How much compute was used to train DETR?

Around 4 × 10²⁰ FLOP, on NVIDIA V100. 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.

10

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

11

Would two GPUs run DETR faster?

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

12

Why does the quantisation differ between cards for DETR?

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

13

How accurate are these DETR 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 33,882–90,353 tok/s on the B200 rather than a single number.

14

What GPU do I need to run DETR?

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

15

How fast is DETR on a GPU?

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

16

How much VRAM does DETR need?

About 0.8 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.

17

Can I run DETR on a 8 GB GPU?

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

18

Can I run DETR on a 12 GB GPU?

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

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.