Yuan 2.0 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
Radeon Instinct MI200
64 GB · IQ4_XS · 13.0 tok/s
Fastest card
B200
33.0 tok/s · 180 GB
Which GPUs can run Yuan 2.0?
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.
43 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
33.0
tok/s
20–53 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 110.5 GB | Q8_0 | Comfortable |
|
33.0
tok/s
20–53 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 110.5 GB | Q8_0 | Comfortable |
|
32.0
tok/s
19–51 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 62.8 GB | Q4_K_M | Tight |
|
32.0
tok/s
19–51 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 62.8 GB | Q4_K_M | Tight |
|
29.1
tok/s
17–46 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 74.7 GB | Q5_K_M | Tight |
|
26.4
tok/s
16–42 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 110.5 GB | Q8_0 | Comfortable |
|
26.4
tok/s
16–42 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 110.5 GB | Q8_0 | Comfortable |
|
24.8
tok/s
15–40 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 74.7 GB | Q5_K_M | Tight |
|
24.8
tok/s
15–40 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 74.7 GB | Q5_K_M | Tight |
|
24.8
tok/s
15–40 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 74.7 GB | Q5_K_M | Tight |
|
21.1
tok/s
13–34 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 110.5 GB | Q8_0 | Tight |
|
20.5
tok/s
12–33 · low confidence |
H100 SXM5 64 GB NVIDIA | 64 GB | 2,020 GB/s | Mar 2023 | 56.8 GB | IQ4_XS | Tight |
|
20.2
tok/s
12–32 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 110.5 GB | Q8_0 | Tight |
|
20.2
tok/s
12–32 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 110.5 GB | Q8_0 | Tight |
|
19.4
tok/s
12–31 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 62.8 GB | Q4_K_M | Tight |
|
19.4
tok/s
12–31 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 62.8 GB | Q4_K_M | Tight |
|
19.4
tok/s
12–31 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 62.8 GB | Q4_K_M | Tight |
|
19.4
tok/s
12–31 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 62.8 GB | Q4_K_M | Tight |
|
19.4
tok/s
12–31 · low confidence |
H100 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Oct 2022 | 62.8 GB | Q4_K_M | Tight |
|
19.4
tok/s
12–31 · low confidence |
H800 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 62.8 GB | Q4_K_M | Tight |
|
19.3
tok/s
12–31 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 110.5 GB | Q8_0 | Comfortable |
|
18.5
tok/s
11–30 · low confidence |
A100 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Jun 2021 | 62.8 GB | Q4_K_M | Tight |
|
18.5
tok/s
11–30 · low confidence |
A800 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Nov 2022 | 62.8 GB | Q4_K_M | Tight |
|
17.2
tok/s
10–27 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 110.5 GB | Q8_0 | Tight |
|
17.2
tok/s
10–27 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 110.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
- Inspur
- Organisation type
- Industry
- Country
- China
- Published
- 27 November 2023
- Authors
- Shaohua Wu, Xudong Zhao, Shenling Wang, Jiangang Luo, Lingjun Li, Xi Chen, Bing Zhao, Wei Wang, Tong Yu, Rongguo Zhang, Jiahua Zhang, Chao Wang
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Translation, Code generation
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
- 102.6B
- Training data
- tokens
- Epochs
- 1
102.6 billion
Most likely the 288B tokens do not represent multiple epochs. As a sense check, Table 2 appears to indicate that 5.73% of pre-training tokens come from synthetically generated text output by GPT-3.5. If the full training corpus is 288B tokens, this would imply ~$24k in API costs at $1.50/1M tokens to generate the data, which 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
- 1.8 × 10²³ FLOP
- How it was established
- Operation counting
Trained on 288B tokens 6*102.6b*288b = 1.78e23
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 (restricted use)
- Training code
- Open source
- Hugging Face
- IEITYuan
commercial ok, but nothing that "may cause harm to the country and society, or for any services that have not undergone security assessment and filing" https://huggingface.co/IEITYuan/Yuan2-102B-hf https://github.com/IEIT-Yuan/Yuan-2.0?tab=License-1-ov-file
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Likely above 10²³ FLOP
- Yes
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- YUAN 2.0: A Large Language Model with Localized Filtering-based Attention
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Yuan 2.0
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 33.0 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 33.0 tok/s
- 03 H800 SXM5 80 GB · 3,360 GB/s · Q4_K_M 32.0 tok/s
- 04 H100 SXM5 80 GB 80 GB · 3,360 GB/s · Q4_K_M 32.0 tok/s
- 05 H100 NVL 94 GB 94 GB · 3,940 GB/s · Q5_K_M 29.1 tok/s
- 06 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 26.4 tok/s
- 07 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 26.4 tok/s
- 08 H100 PCIe 96 GB 96 GB · 3,360 GB/s · Q5_K_M 24.8 tok/s
- 09 H100 SXM5 94 GB 94 GB · 3,360 GB/s · Q5_K_M 24.8 tok/s
- 10 H100 SXM5 96 GB 96 GB · 3,360 GB/s · Q5_K_M 24.8 tok/s
The smallest GPUs that still run Yuan 2.0
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Jetson T4000 64 GB · needs 56.8 GB · IQ4_XS · tight 2.8 tok/s
- 02 H100 SXM5 64 GB 64 GB · needs 56.8 GB · IQ4_XS · tight 20.5 tok/s
- 03 Jetson AGX Orin 64 GB 64 GB · needs 56.8 GB · IQ4_XS · tight 2.1 tok/s
- 04 Radeon Instinct MI200 64 GB · needs 56.8 GB · IQ4_XS · tight 13.0 tok/s
- 05 Radeon Instinct MI210 64 GB · needs 56.8 GB · IQ4_XS · tight 13.0 tok/s
- 06 RTX PRO 5000 72 GB Blackwell 72 GB · needs 62.8 GB · Q4_K_M · tight 12.8 tok/s
- 07 H100 CNX 80 GB · needs 62.8 GB · Q4_K_M · tight 19.4 tok/s
- 08 H800 PCIe 80 GB 80 GB · needs 62.8 GB · Q4_K_M · tight 19.4 tok/s
- 09 H800 SXM5 80 GB · needs 62.8 GB · Q4_K_M · tight 32.0 tok/s
- 10 A800 PCIe 80 GB 80 GB · needs 62.8 GB · Q4_K_M · tight 18.5 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Radeon Instinct MI200
Memory needed
56.8 GB
Fastest
33.0 tok/s
Yuan 2.0 sits at 102.6B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 43 of the cards we track can hold it.
The smallest card that holds it is the Radeon Instinct MI200 with 64 GB, running it at IQ4_XS and producing around 13.0 tokens per second.
A B200 is the fastest we calculate for it: about 33.0 tokens per second, from 8,000 GB/s of memory bandwidth.
About this model
Yuan 2.0 was published by Inspur, in China, in November 2023. The organisation is categorised as industry.
It works in Language, and is recorded as doing language modeling/generation, Translation, Code generation.
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. It is published under the IEITYuan organisation on Hugging Face.
How fast it runs, and why
Half the cards that hold it manage more than 18.5 tokens per second, and 37 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.
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
The training run consumed about 1.8 × 10²³ FLOP. That figure describes the cost of creating it and has no bearing on how quickly it generates text.
Step by step
How to choose a GPU for Yuan 2.0
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Read the memory figure first
The table lists every card that can hold Yuan 2.0 — around 56.8 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
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Yuan 2.0.
-
03
Set a quality floor
The quantisation column varies by card, because a bigger card holds a more accurate copy of Yuan 2.0 — IQ4_XS on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for Yuan 2.0. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 33.0 tok/s.
-
05
Read the fit column last
The fit column separates cards that just manage Yuan 2.0 from those with room to spare. Buy for the second if the context might grow.
-
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 Yuan 2.0 is settled.
Answers
Yuan 2.0 — common questions
Can I run Yuan 2.0 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 19.6 GB. Our figures for Yuan 2.0 assume it is fully resident.
Would two GPUs run Yuan 2.0 faster?
A second card roughly doubles the memory available but not the generation rate. With 43 cards already able to run Yuan 2.0 alone, the case for pairing is weak.
Why does the quantisation differ between cards for Yuan 2.0?
Each card is shown running the least-compressed copy it can hold, and Yuan 2.0 appears at 4 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these Yuan 2.0 speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 20–53 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
What GPU do I need to run Yuan 2.0?
The smallest card in our catalogue that holds Yuan 2.0 is the Radeon Instinct MI200, with 64 GB of memory. It runs the model at IQ4_XS using about 56.8 GB, and produces roughly 13.0 tokens per second. 43 cards in total can run it.
How fast is Yuan 2.0 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 33.0 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 37 of the cards that can run Yuan 2.0 clear that.
How much VRAM does Yuan 2.0 need?
About 56.8 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.
Is Yuan 2.0 open source?
Its weights are published, so Yuan 2.0 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 Yuan 2.0 have?
Yuan 2.0 has 102.6B parameters. 102.6 billion. 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 Yuan 2.0?
Yuan 2.0 was published by Inspur, based in China, categorised as industry.
When was Yuan 2.0 released?
Yuan 2.0 was published in November 2023. 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 Yuan 2.0 used for?
Yuan 2.0 works in Language, and is recorded as handling language modeling/generation, Translation, Code generation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download Yuan 2.0?
Its weights are published under the IEITYuan organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train Yuan 2.0?
Around 1.8 × 10²³ FLOP. 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.
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.