YOLOX-X 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 · 372 tok/s
Fastest card
B200
34,190 tok/s · 180 GB
Which GPUs can run YOLOX-X?
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 | |||||
|---|---|---|---|---|---|---|---|
|
34,190
tok/s
20,514–54,704 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 0.8 GB | Q8_0 | Comfortable |
|
34,190
tok/s
20,514–54,704 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 0.8 GB | Q8_0 | Comfortable |
|
27,302
tok/s
16,381–43,683 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.8 GB | Q8_0 | Comfortable |
|
27,302
tok/s
16,381–43,683 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 0.8 GB | Q8_0 | Comfortable |
|
21,835
tok/s
13,101–34,935 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
20,899
tok/s
12,539–33,438 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.8 GB | Q8_0 | Comfortable |
|
20,899
tok/s
12,539–33,438 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 0.8 GB | Q8_0 | Comfortable |
|
20,001
tok/s
12,001–32,002 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 0.8 GB | Q8_0 | Comfortable |
|
17,751
tok/s
10,651–28,402 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
17,751
tok/s
10,651–28,402 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
17,751
tok/s
10,651–28,402 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 0.8 GB | Q8_0 | Comfortable |
|
16,839
tok/s
10,103–26,942 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
14,360
tok/s
8,616–22,976 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
14,360
tok/s
8,616–22,976 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 0.8 GB | Q8_0 | Comfortable |
|
14,360
tok/s
8,616–22,976 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
14,360
tok/s
8,616–22,976 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
14,360
tok/s
8,616–22,976 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 0.8 GB | Q8_0 | Comfortable |
|
10,934
tok/s
6,560–17,494 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.8 GB | Q8_0 | Comfortable |
|
10,934
tok/s
6,560–17,494 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 0.8 GB | Q8_0 | Comfortable |
|
9,112
tok/s
5,467–14,579 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
8,917
tok/s
5,350–14,268 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 0.8 GB | Q8_0 | Comfortable |
|
8,718
tok/s
5,231–13,950 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 0.8 GB | Q8_0 | Comfortable |
|
8,718
tok/s
5,231–13,950 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 0.8 GB | Q8_0 | Comfortable |
|
8,718
tok/s
5,231–13,950 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 0.8 GB | Q8_0 | Comfortable |
|
8,718
tok/s
5,231–13,950 · 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
- Megvii Inc
- Organisation type
- Industry
- Country
- China
- Published
- 6 August 2021
- Authors
- Zheng Ge, Songtao Liu, Feng Wang, Zeming Li, Jian Sun
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
- 99.1M
- Training data
- 2,500,000 tokens
- Epochs
- 300
- Batch size
- 128
99.1M, table 3
2.5 million image-label pairs, per Coco paper https://arxiv.org/abs/1405.0312
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
- 6.3 × 10²⁰ FLOP
- How it was established
- Operation counting
"We train the models for a total of 300 epochs with 5 epochs warmup on COCO train2017 [17]. We use stochastic gradient descent (SGD) for training ... The batch size is 128 by default to typical 8-GPU devices ... input size is evenly drawn from 448 to 832 with 32 strides" Training is done on 300 epochs of the 2.5 million image-label pairs in COCO train2017. Table 3 indicates 281.9 GFLOP per forward pass on a 640x640 image. The mean image width/height is 640, though using this to estimate traini…
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
- Chips used
- 8
- Power draw
- 4.8 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
Apache 2.0 for code/weights https://github.com/Megvii-BaseDetection/YOLOX/blob/main/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
- Highly cited,SOTA improvement
- Record confidence
- Likely
- Citations
- 5,755
Table 6
Sources
Where this record came from and when it was last checked.
- Reference
- YOLOX: Exceeding YOLO Series in 2021
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run YOLOX-X
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 34,190 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 34,190 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 27,302 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 27,302 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 21,835 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 20,899 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 20,899 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 20,001 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 17,751 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 17,751 tok/s
The smallest GPUs that still run YOLOX-X
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 410 tok/s
- 02 RTX A400 4 GB · needs 0.8 GB · Q8_0 · comfortable 410 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 0.8 GB · Q8_0 · comfortable 547 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 0.8 GB · Q8_0 · comfortable 821 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 0.8 GB · Q8_0 · comfortable 146 tok/s
- 06 Radeon RX 6450M 4 GB · needs 0.8 GB · Q8_0 · comfortable 427 tok/s
- 07 Radeon RX 6550M 4 GB · needs 0.8 GB · Q8_0 · comfortable 480 tok/s
- 08 Radeon RX 6550S 4 GB · needs 0.8 GB · Q8_0 · comfortable 427 tok/s
- 09 Arc A310 4 GB · needs 0.8 GB · Q8_0 · comfortable 344 tok/s
- 10 Arc Pro A30M 4 GB · needs 0.8 GB · Q8_0 · comfortable 356 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Tesla C1080
Memory needed
0.8 GB
Fastest
34,190 tok/s
YOLOX-X reaches a parameter count of 99.1M. 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 smallest card that holds it is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 372 tokens per second.
The fastest we calculate for it is B200, generating roughly 34,190 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
What this model is
YOLOX-X was published by Megvii Inc, in the country recorded as China, during August 2021. The category the publisher falls under is industry.
It works in the domain of Vision, and is recorded as performing the task of object detection.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.
What decides the speed
The median result is around 960.1 tokens per second. Exceeding reading speed outright: 818 of them.
Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.
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.
What went into building it
Training it took a computation budget of roughly 6.3 × 10²⁰ FLOP, on hardware recorded as NVIDIA V100. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The training set ran to roughly 2,500,000 tokens of text.
It is tracked in the underlying dataset for one reason in particular: highly cited,SOTA improvement.
Step by step
How to choose a GPU for YOLOX-X
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Start from the memory column
Every card here has been checked against YOLOX-X, needing around 0.8 GB at a compression of Q8_0. Capacity is the gate — a card either holds it or it does not.
-
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 YOLOX-X.
-
03
Set a quality floor
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
Sort by speed to see how cards rank for YOLOX-X. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 34,190 tok/s.
-
05
Read the fit column last
The fit column separates cards that just manage it from those with room to spare, in the case of YOLOX-X. 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
Check the card from the other side
Following a card through to its own page shows every other model it can hold, which is the question that follows once you have settled on YOLOX-X.
Answers
YOLOX-X — common questions
YOLOX-X— 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.
YOLOX-X— how many parameters does it have?
It has a parameter count of 99.1M. 99.1M, table 3. 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.
YOLOX-X— who created it?
It was published by Megvii Inc, based in China, an organisation categorised as industry.
YOLOX-X— when was it released?
It was published in August 2021. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
YOLOX-X— what is it used for?
It works in the domain of Vision, and is recorded as handling the task of object detection. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.
YOLOX-X— 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.
YOLOX-X— how much compute was used to train it?
Training consumed around 6.3 × 10²⁰ FLOP, on hardware recorded as 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.
YOLOX-X— 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.
YOLOX-X— 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.
YOLOX-X— why does the quantisation differ between cards?
Because capacity varies, so does how hard it has to be squeezed. The number of distinct levels in the table above: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
YOLOX-X— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 20,514–54,704 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
YOLOX-X— 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.8 GB, and produces roughly 372 tokens per second. The number of cards able to run it in total: 818.
YOLOX-X— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 34,190 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.
YOLOX-X— how much VRAM does it need?
It needs about 0.8 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.
YOLOX-X— 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.8 GB and generating roughly 6,368 tokens per second. The fit is comfortable.
YOLOX-X— 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.8 GB and generating roughly 3,899 tokens per second. The fit is comfortable.
YOLOX-X— 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.8 GB and generating roughly 4,829 tokens per second. The fit is comfortable.
YOLOX-X— 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.8 GB and generating roughly 5,727 tokens per second. The fit is comfortable.
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.