Yi-34B 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
RTX A4500
20 GB · Q3_K_M · 21.5 tok/s
Fastest card
B200
99.7 tok/s · 180 GB
Which GPUs can run Yi-34B?
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.
132 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
99.7
tok/s
60–159 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 37.1 GB | Q8_0 | Comfortable |
|
99.7
tok/s
60–159 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 37.1 GB | Q8_0 | Comfortable |
|
79.6
tok/s
48–127 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 37.1 GB | Q8_0 | Comfortable |
|
79.6
tok/s
48–127 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 37.1 GB | Q8_0 | Comfortable |
|
63.6
tok/s
38–102 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 37.1 GB | Q8_0 | Comfortable |
|
60.9
tok/s
37–97 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 37.1 GB | Q8_0 | Comfortable |
|
60.9
tok/s
37–97 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 37.1 GB | Q8_0 | Comfortable |
|
58.3
tok/s
35–93 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 37.1 GB | Q8_0 | Comfortable |
|
51.7
tok/s
31–83 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 37.1 GB | Q8_0 | Comfortable |
|
51.7
tok/s
31–83 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 37.1 GB | Q8_0 | Comfortable |
|
51.7
tok/s
31–83 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 37.1 GB | Q8_0 | Comfortable |
|
49.1
tok/s
29–79 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 37.1 GB | Q8_0 | Comfortable |
|
41.9
tok/s
25–67 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 37.1 GB | Q8_0 | Comfortable |
|
41.9
tok/s
25–67 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 37.1 GB | Q8_0 | Comfortable |
|
41.9
tok/s
25–67 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 37.1 GB | Q8_0 | Comfortable |
|
41.9
tok/s
25–67 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 37.1 GB | Q8_0 | Comfortable |
|
41.9
tok/s
25–67 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 37.1 GB | Q8_0 | Comfortable |
|
41.6
tok/s
25–67 · low confidence |
DRIVE A100 PROD NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 25.2 GB | Q5_K_M | Tight |
|
41.6
tok/s
25–67 · low confidence |
GRID A100A NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 25.2 GB | Q5_K_M | Tight |
|
39.8
tok/s
24–64 · low confidence |
GeForce RTX 5090 NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 25.2 GB | Q5_K_M | Tight |
|
39.8
tok/s
24–64 · low confidence |
GeForce RTX 5090 D NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 25.2 GB | Q5_K_M | Tight |
|
38.5
tok/s
23–62 · low confidence |
GeForce RTX 5090 D V2 NVIDIA | 24 GB | 1,340 GB/s | Aug 2025 | 21.3 GB | Q4_K_M | Tight |
|
35.1
tok/s
21–56 · low confidence |
A30X NVIDIA | 24 GB | 1,220 GB/s | Apr 2021 | 21.3 GB | Q4_K_M | Tight |
|
31.9
tok/s
19–51 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 37.1 GB | Q8_0 | Comfortable |
|
31.9
tok/s
19–51 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 37.1 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
- 01.AI
- Organisation type
- Industry
- Country
- China
- Published
- 2 November 2023
- Authors
- Alex Young, Bei Chen, Chao Li, Chengen Huang, Ge Zhang, Guanwei Zhang, Heng Li, Jiangcheng Zhu, Jianqun Chen, Jing Chang, Kaidong Yu, Peng Liu, Qiang Liu, Shawn Yue, Senbin Yang, Shiming Yang, Tao Yu, Wen Xie, Wenhao Huang, Xiaohui Hu, Xiaoyi Ren, Xinyao Niu, Pengcheng Nie, Yuchi Xu, Yudong Liu, Yue Wang, Yuxuan Cai, Zhenyu Gu, Zhiyuan Liu, Zonghong Dai
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Chat, Language modeling/generation, Translation, Code generation
- 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
- 34B
- Training data
- 3,100,000,000,000 tokens
34b
"language models pretrained from scratch on 3.1T highly-engineered large amount of data, and finetuned on a small but meticulously polished alignment data."
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.1 × 10²³ FLOP
- How it was established
- Operation counting
"The dataset we use contains Chinese & English only. We used approximately 3T tokens" sounds like this means it was trained on 3T tokens, not necessarily that the dataset contains 3T tokens? If so, 34b * 3T * 6 = 6.1e23
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 A100
- Chips used
- 128
- Power draw
- 101.6 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 (restricted use)
- Training code
- Unreleased
- Hugging Face
- 01-ai
apply for commercial license: no training code https://github.com/01-ai/Yi/blob/main/MODEL_LICENSE_AGREEMENT.txt the model https://huggingface.co/01-ai/Yi-34B-Chat Apache 2.0 "If you create derivative works based on this model, please include the following attribution in your derivative works: ...."
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
- Why it is tracked
- Significant use
- Record confidence
- Confident
2nd most popular model on HuggingFace: https://decrypt.co/206195/new-open-source-ai-model-from-china-boasts-twice-the-capacity-of-chatgpt also maybe the best open-source model, does better than Llama 2-70B on several benchmarks
Sources
Where this record came from and when it was last checked.
- Reference
- Yi: Open Foundation Models by 01.AI
- Last updated
- 18 December 2025
The extremes
The ten fastest GPUs that run Yi-34B
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 99.7 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 99.7 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 79.6 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 79.6 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 63.6 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 60.9 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 60.9 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 58.3 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 51.7 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 51.7 tok/s
The smallest GPUs that still run Yi-34B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 RTX 4000 Ada Generation 20 GB · needs 17.3 GB · Q3_K_M · tight 12.1 tok/s
- 02 RTX 4000 SFF Ada Generation 20 GB · needs 17.3 GB · Q3_K_M · tight 9.4 tok/s
- 03 Radeon RX 7900 XT 20 GB · needs 17.3 GB · Q3_K_M · tight 21.0 tok/s
- 04 A10M 20 GB · needs 17.3 GB · Q3_K_M · tight 16.8 tok/s
- 05 GeForce RTX 3080 Ti 20 GB 20 GB · needs 17.3 GB · Q3_K_M · tight 25.6 tok/s
- 06 RTX A4500 20 GB · needs 17.3 GB · Q3_K_M · tight 21.5 tok/s
- 07 Arc Pro B60 24 GB · needs 21.3 GB · Q4_K_M · tight 8.5 tok/s
- 08 GeForce RTX 5090 D V2 24 GB · needs 21.3 GB · Q4_K_M · tight 38.5 tok/s
- 09 RTX PRO 4000 Blackwell SFF 24 GB · needs 21.3 GB · Q4_K_M · tight 12.4 tok/s
- 10 GeForce RTX 5090 Mobile 24 GB · needs 21.3 GB · Q4_K_M · tight 25.8 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
RTX A4500
Memory needed
17.3 GB
Fastest
99.7 tok/s
Yi-34B reaches a parameter count of 34B. That lands in the range a serious desktop card can handle once the weights are compressed. The number of cards we track that can run it: 132.
The entry point is RTX A4500, with a memory capacity of 20 GB, running it at a compression of Q3_K_M and producing around 21.5 tokens per second.
At the other end sits B200, generating roughly 99.7 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Where it came from
Yi-34B was published by 01.AI, in the country recorded as China, during November 2023. The category the publisher falls under is industry.
It works in the domain of Language, and is recorded as performing the task of chat, Language modeling/generation, Translation, Code generation.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. On Hugging Face it is published under the organisation 01-ai.
Understanding the speeds
Across every card that can run it, the middle of the range sits at 21.2 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 103 of them.
It is a dense model, so every parameter is read for every token produced. That makes speed track memory bandwidth almost exactly — a card with twice the bandwidth generates roughly twice as fast.
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
Producing it required arithmetic totalling around 6.1 × 10²³ FLOP, on hardware recorded as NVIDIA A100. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The training set ran to roughly 3,100,000,000,000 tokens of text.
The reason it appears in this catalogue at all: significant use.
Step by step
How to choose a GPU for Yi-34B
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
Start from what it actually needs, which is the requirement of Yi-34B, needing around 17.3 GB at a compression of Q3_K_M. Capacity is the gate — a card either holds it or it does not.
-
02
Set the context length you will work at
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 Yi-34B.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold, reaching a compression of Q3_K_M 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
Compare tokens per second, not specifications
Sort by speed to see how cards rank for Yi-34B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 99.7 tok/s.
-
05
Look at the headroom, not just the fit
The fit column separates cards that just manage it from those with room to spare, in the case of Yi-34B. 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
Open the card you have settled on
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 Yi-34B.
Answers
Yi-34B — common questions
Yi-34B— how many parameters does it have?
It has a parameter count of 34B. 34b. 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.
Yi-34B— who created it?
It was published by 01.AI, based in China, an organisation categorised as industry.
Yi-34B— when was it released?
It 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.
Yi-34B— what is it used for?
It works in the domain of Language, and is recorded as handling the task of chat, Language modeling/generation, Translation, Code generation. These are the areas it was designed around; they describe intent rather than a hard boundary.
Yi-34B— where can I download it?
Its weights are published on Hugging Face, under the organisation 01-ai. We do not host model files — this site calculates what hardware is needed to run them.
Yi-34B— how much compute was used to train it?
Training consumed around 6.1 × 10²³ FLOP, on hardware recorded as NVIDIA A100. 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.
Yi-34B— can I run it if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part held in system memory drags the whole thing down. The nearest miss we calculate falls short by 6.9 GB. Every figure here assumes the whole model is resident on the card.
Yi-34B— would two GPUs run it faster?
Capacity adds across cards; throughput does not. The number of cards already holding it on their own: 132. So a second card is rarely the answer here.
Yi-34B— why does the quantisation differ between cards?
Each card is shown running the least-compressed copy it can hold. The number of distinct compression levels across the cards that fit it: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Yi-34B— how accurate are these speed estimates?
These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 60–159 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Yi-34B— what GPU do I need to run it?
The smallest card in our catalogue that holds it is RTX A4500, with a memory capacity of 20 GB. It runs the model at a compression of Q3_K_M using about 17.3 GB, and produces roughly 21.5 tokens per second. The number of cards able to run it in total: 132.
Yi-34B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 99.7 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: 103.
Yi-34B— how much VRAM does it need?
It needs about 17.3 GB at a compression of Q3_K_M, 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.
Yi-34B— 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 Q4_K_M, using about 21.3 GB and generating roughly 38.5 tokens per second. The fit is tight.
Yi-34B— 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.
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.