PLATO-XL 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
Xeon Phi 5110P
8 GB · IQ4_XS · 19.7 tok/s
Fastest card
B200
308 tok/s · 180 GB
Which GPUs can run PLATO-XL?
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.
509 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
308
tok/s
185–493 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 12.5 GB | Q8_0 | Comfortable |
|
308
tok/s
185–493 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 12.5 GB | Q8_0 | Comfortable |
|
246
tok/s
148–394 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 12.5 GB | Q8_0 | Comfortable |
|
246
tok/s
148–394 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 12.5 GB | Q8_0 | Comfortable |
|
197
tok/s
118–315 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 12.5 GB | Q8_0 | Comfortable |
|
188
tok/s
113–301 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 12.5 GB | Q8_0 | Comfortable |
|
188
tok/s
113–301 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 12.5 GB | Q8_0 | Comfortable |
|
180
tok/s
108–288 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 12.5 GB | Q8_0 | Comfortable |
|
160
tok/s
96–256 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 12.5 GB | Q8_0 | Comfortable |
|
160
tok/s
96–256 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 12.5 GB | Q8_0 | Comfortable |
|
160
tok/s
96–256 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 12.5 GB | Q8_0 | Comfortable |
|
152
tok/s
91–243 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
141
tok/s
85–225 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 6.7 GB | IQ4_XS | Tight |
|
129
tok/s
78–207 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
129
tok/s
78–207 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 12.5 GB | Q8_0 | Comfortable |
|
107
tok/s
64–172 · low confidence |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.6 GB | Q5_K_M | Tight |
|
98.5
tok/s
59–158 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 12.5 GB | Q8_0 | Comfortable |
|
98.5
tok/s
59–158 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 12.5 GB | Q8_0 | Comfortable |
|
82.1
tok/s
49–131 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 12.5 GB | Q8_0 | Comfortable |
|
80.3
tok/s
48–129 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 12.5 GB | Q8_0 | Comfortable |
|
78.6
tok/s
47–126 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 12.5 GB | Q8_0 | Comfortable |
|
78.6
tok/s
47–126 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 12.5 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
- Baidu
- Organisation type
- Industry
- Country
- China
- Published
- 20 September 2021
- Authors
- Siqi Bao, Huang He, Fan Wang, Hua Wu, Haifeng Wang, Wenquan Wu, Zhihua Wu, Zhen Guo, Hua Lu, Xinxian Huang, Xin Tian, Xinchao Xu, Yingzhan Lin, Zheng-Yu Niu
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling
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
- 11B
- Training data
- 150,000,000,000 tokens
"In PLATO-XL, each model was trained for a total of 150B tokens, with a batch size of 2M tokens." 811M English and 1.2B Chinese (context, response) samples. So if the average response is at least 75 tokens, the 150B tokens seen in training don't include repeat tokens. This seems plausible.
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
- 9.9 × 10²¹ FLOP
- How it was established
- Operation counting
"In PLATO-XL, each model was trained for a total of 150B tokens, with a batch size of 2M tokens." 150B * 11B * 6 = 9.9e21
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
- 256
- Power draw
- 155.0 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
- Unreleased
apache 2.0 https://github.com/PaddlePaddle/Knover/tree/develop/projects/PLATO-XL
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
- Record confidence
- Confident
- Citations
- 69
Table 4
Sources
Where this record came from and when it was last checked.
- Reference
- PLATO-XL: Exploring the Large-scale Pre-training of Dialogue Generation
- Last updated
- 1 December 2025
The extremes
The ten fastest GPUs that run PLATO-XL
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 308 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 308 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 246 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 246 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 197 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 188 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 188 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 180 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 160 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 160 tok/s
The smallest GPUs that still run PLATO-XL
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Radeon RX 7400 8 GB · needs 6.7 GB · IQ4_XS · tight 21.2 tok/s
- 02 Radeon RX 9060 8 GB · needs 6.7 GB · IQ4_XS · tight 23.8 tok/s
- 03 GeForce RTX 5050 8 GB · needs 6.7 GB · IQ4_XS · tight 30.3 tok/s
- 04 GeForce RTX 5050 Mobile 8 GB · needs 6.7 GB · IQ4_XS · tight 36.3 tok/s
- 05 Radeon RX 9060 XT 8 GB 8 GB · needs 6.7 GB · IQ4_XS · tight 23.8 tok/s
- 06 GeForce RTX 5060 Mobile 8 GB · needs 6.7 GB · IQ4_XS · tight 36.3 tok/s
- 07 GeForce RTX 5060 8 GB · needs 6.7 GB · IQ4_XS · tight 42.4 tok/s
- 08 GeForce RTX 5060 Ti 8 GB 8 GB · needs 6.7 GB · IQ4_XS · tight 42.4 tok/s
- 09 GeForce RTX 5070 Mobile 8 GB · needs 6.7 GB · IQ4_XS · tight 36.3 tok/s
- 10 Radeon RX 7650 GRE 8 GB · needs 6.7 GB · IQ4_XS · tight 21.2 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Xeon Phi 5110P
Memory needed
6.7 GB
Fastest
308 tok/s
PLATO-XL is small enough at 11B parameters that hardware is rarely the obstacle — 509 of the cards we track can run it, including cards several years old.
The smallest card that holds it is the Xeon Phi 5110P with 8 GB, running it at IQ4_XS and producing around 19.7 tokens per second.
A B200 is the fastest we calculate for it: about 308 tokens per second, from 8,000 GB/s of memory bandwidth.
Where it came from
PLATO-XL was published by Baidu, in China, in September 2021. industry is the category the publisher falls under.
It works in Language, and is recorded as doing language modeling.
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.
Understanding the speeds
The median result is around 21.2 tokens per second; 460 cards produce text faster than most people read it.
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.
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
Producing it required around 9.9 × 10²¹ FLOP of arithmetic, on NVIDIA V100, which is a statement about the training budget rather than about inference.
The training set ran to roughly 150,000,000,000 tokens.
The reason it appears in this catalogue at all is sOTA improvement.
Step by step
How to choose a GPU for PLATO-XL
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
The table lists every card that can hold PLATO-XL — around 6.7 GB at IQ4_XS. That figure, not the card's headline performance, is what decides whether it runs.
-
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 PLATO-XL can slip off a card that handles short questions easily.
-
03
Decide how much compression you will accept
The quantisation column varies by card, because a bigger card holds a more accurate copy of PLATO-XL — IQ4_XS on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Rank by throughput rather than spec sheet
Ranking by tokens per second for PLATO-XL follows memory bandwidth, not core counts, which is why the B200 tops it at 308 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs PLATO-XL but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
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 PLATO-XL is settled.
Answers
PLATO-XL — common questions
How fast is PLATO-XL on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 308 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 460 of the cards that can run PLATO-XL clear that.
How much VRAM does PLATO-XL need?
About 6.7 GB at IQ4_XS 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 PLATO-XL on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at IQ4_XS, using about 6.7 GB and generating roughly 141 tokens per second — a tight fit.
Can I run PLATO-XL on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q6_K, using about 9.9 GB and generating roughly 51.0 tokens per second — a tight fit.
Can I run PLATO-XL on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 12.5 GB and generating roughly 43.5 tokens per second — a tight fit.
Can I run PLATO-XL on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 12.5 GB and generating roughly 51.6 tokens per second — a comfortable fit.
Is PLATO-XL open source?
Its weights are published, so PLATO-XL 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 PLATO-XL have?
PLATO-XL has 11B parameters. 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 PLATO-XL?
PLATO-XL was published by Baidu, based in China, categorised as industry.
When was PLATO-XL released?
PLATO-XL was published in September 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.
What is PLATO-XL used for?
PLATO-XL works in Language, and is recorded as handling language modeling. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download PLATO-XL?
The weights for PLATO-XL are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train PLATO-XL?
Around 9.9 × 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.
Can I run PLATO-XL if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down — the nearest miss we calculate is short by 2.0 GB. Our figures for PLATO-XL assume it is fully resident.
Would two GPUs run PLATO-XL faster?
A second card roughly doubles the memory available but not the generation rate. With 509 cards already able to run PLATO-XL alone, the case for pairing is weak.
Why does the quantisation differ between cards for PLATO-XL?
Each card is shown running the least-compressed copy it can hold, and PLATO-XL appears at 4 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these PLATO-XL 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 185–493 tok/s on the B200 rather than a single number.
What GPU do I need to run PLATO-XL?
The smallest card in our catalogue that holds PLATO-XL is the Xeon Phi 5110P, with 8 GB of memory. It runs the model at IQ4_XS using about 6.7 GB, and produces roughly 19.7 tokens per second. 509 cards in total can run it.
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.