EfficientDet 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 · 479 tok/s
Fastest card
B200
44,003 tok/s · 180 GB
Which GPUs can run EfficientDet?
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 | |||||
|---|---|---|---|---|---|---|---|
|
44,003
tok/s
26,402–70,405 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 0.8 GB | Q8_0 | Comfortable |
|
44,003
tok/s
26,402–70,405 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 0.8 GB | Q8_0 | Comfortable |
|
35,138
tok/s
21,083–56,220 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.8 GB | Q8_0 | Comfortable |
|
35,138
tok/s
21,083–56,220 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.8 GB | Q8_0 | Comfortable |
|
28,101
tok/s
16,861–44,962 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
26,897
tok/s
16,138–43,035 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.8 GB | Q8_0 | Comfortable |
|
26,897
tok/s
16,138–43,035 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.8 GB | Q8_0 | Comfortable |
|
25,742
tok/s
15,445–41,187 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 0.8 GB | Q8_0 | Comfortable |
|
22,846
tok/s
13,708–36,553 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
22,846
tok/s
13,708–36,553 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
22,846
tok/s
13,708–36,553 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
21,672
tok/s
13,003–34,674 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
18,481
tok/s
11,089–29,570 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
18,481
tok/s
11,089–29,570 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 0.8 GB | Q8_0 | Comfortable |
|
18,481
tok/s
11,089–29,570 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
18,481
tok/s
11,089–29,570 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
18,481
tok/s
11,089–29,570 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
14,072
tok/s
8,443–22,515 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.8 GB | Q8_0 | Comfortable |
|
14,072
tok/s
8,443–22,515 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.8 GB | Q8_0 | Comfortable |
|
11,727
tok/s
7,036–18,763 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
11,477
tok/s
6,886–18,362 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
11,221
tok/s
6,732–17,953 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 0.8 GB | Q8_0 | Comfortable |
|
11,221
tok/s
6,732–17,953 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 0.8 GB | Q8_0 | Comfortable |
|
11,221
tok/s
6,732–17,953 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 0.8 GB | Q8_0 | Comfortable |
|
11,221
tok/s
6,732–17,953 · 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
- Google Brain
- Organisation type
- Industry
- Country
- United States of America
- Published
- 27 July 2020
- Authors
- Mingxing Tan, Ruoming Pang, Quoc V. Le
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision
- Task
- Object detection
- Numerical format
- FP16
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
- 77M
- Training data
- tokens
- Epochs
- 600
"EfficientDet-D7 achieves stateof-the-art 55.1 AP on COCO test-dev with 77M parameters and 410B FLOPs"
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
Repo is Apache 2.0: https://github.com/google/automl/tree/master/efficientdet
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,SOTA improvement
- Citations
- 6,849
"EfficientDet-D7 achieves stateof-the-art 55.1 AP on COCO test-dev with 77M parameters and 410B FLOPs"
Sources
Where this record came from and when it was last checked.
- Reference
- EfficientDet: Scalable and Efficient Object Detection
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run EfficientDet
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 44,003 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 44,003 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 35,138 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 35,138 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 28,101 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 26,897 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 26,897 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 25,742 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 22,846 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 22,846 tok/s
The smallest GPUs that still run EfficientDet
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.8 GB · Q8_0 · comfortable 528 tok/s
- 02 RTX A400 4 GB · needs 0.8 GB · Q8_0 · comfortable 528 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 0.8 GB · Q8_0 · comfortable 704 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 0.8 GB · Q8_0 · comfortable 1,056 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 0.8 GB · Q8_0 · comfortable 188 tok/s
- 06 Radeon RX 6450M 4 GB · needs 0.8 GB · Q8_0 · comfortable 549 tok/s
- 07 Radeon RX 6550M 4 GB · needs 0.8 GB · Q8_0 · comfortable 618 tok/s
- 08 Radeon RX 6550S 4 GB · needs 0.8 GB · Q8_0 · comfortable 549 tok/s
- 09 Arc A310 4 GB · needs 0.8 GB · Q8_0 · comfortable 443 tok/s
- 10 Arc Pro A30M 4 GB · needs 0.8 GB · Q8_0 · comfortable 458 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
0.8 GB
Fastest
44,003 tok/s
EfficientDet is small enough at 77M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The entry point is the Tesla C1080: 4 GB of memory, Q8_0 compression, roughly 479 tokens per second.
Top of the range is the B200, at roughly 44,003 tokens per second thanks to 8,000 GB/s of bandwidth.
What this model is
EfficientDet was published by Google Brain, in United States of America, in July 2020. It comes out of industry.
It works in Vision, and is recorded as doing object detection.
Published weights mean the model runs on your machine rather than someone else's, which is what makes the hardware question below answerable at all.
What decides the speed
The median result is around 1,235.6 tokens per second; 818 cards produce text faster than most people read it.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
Its internal architecture is not on file, so memory is approximated from the parameter count and marked accordingly. Expect the real figure to differ, more so at long context.
Training and provenance
Its inclusion criterion is highly cited,SOTA improvement.
Step by step
How to choose a GPU for EfficientDet
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
Every card here has been checked against EfficientDet — around 0.8 GB at Q8_0. Capacity is the gate — a card either holds it or it does not.
-
02
Decide how long your conversations run
The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context EfficientDet can slip off a card that handles short questions easily.
-
03
Choose how far you will compress it
Compression is what makes EfficientDet 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.
-
04
Compare tokens per second, not specifications
Ranking by tokens per second for EfficientDet follows memory bandwidth, not core counts, which is why the B200 tops it at 44,003 tok/s.
-
05
Read the fit column last
The fit column separates cards that just manage EfficientDet from those with room to spare. Buy for the second if the context might grow.
-
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. Worth a look before buying for EfficientDet alone — a card is usually bought for more than one model.
Answers
EfficientDet — common questions
What GPU do I need to run EfficientDet?
The smallest card in our catalogue that holds EfficientDet is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 0.8 GB, and produces roughly 479 tokens per second. 818 cards in total can run it.
How fast is EfficientDet on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 44,003 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 EfficientDet clear that.
How much VRAM does EfficientDet 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.
Can I run EfficientDet 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 8,196 tokens per second — a comfortable fit.
Can I run EfficientDet 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 5,019 tokens per second — a comfortable fit.
Can I run EfficientDet 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 6,215 tokens per second — a comfortable fit.
Can I run EfficientDet 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 7,371 tokens per second — a comfortable fit.
Is EfficientDet open source?
Its weights are published, so EfficientDet 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.
How many parameters does EfficientDet have?
EfficientDet has 77M parameters. "EfficientDet-D7 achieves stateof-the-art 55.1 AP on COCO test-dev with 77M parameters and 410B FLOPs". 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.
Who created EfficientDet?
EfficientDet was published by Google Brain, based in United States of America, categorised as industry.
When was EfficientDet released?
EfficientDet was published in July 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.
What is EfficientDet used for?
EfficientDet 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.
Where can I download EfficientDet?
The weights for EfficientDet are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Can I run EfficientDet 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 EfficientDet is rarely worth using. Every figure here assumes the whole model is on the card.
Would two GPUs run EfficientDet faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run EfficientDet alone, the case for pairing is weak.
Why does the quantisation differ between cards for EfficientDet?
Each card is shown running the least-compressed copy it can hold, and EfficientDet appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these EfficientDet speed estimates?
These are estimates with real error bars. The fastest result here, 26,402–70,405 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.
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.