Aquila2 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 Aquila2 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
- Beijing Academy of Artificial Intelligence / BAAI
- Organisation type
- Academia
- Country
- China
- Published
- 13 October 2023
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
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
- 2,000,000,000,000 tokens
34B safetensors say it is 18.2B params There's also a 70B "experimental" version: https://github.com/FlagAI-Open/Aquila2
"we have investigated all 2 trillion tokens of data" from https://github.com/FlagAI-Open/Aquila2
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 SXM4 40 GB
- Chips used
- 512
- Power draw
- 406.5 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
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
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- Aquila2 Technical Report
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Aquila2 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 Aquila2 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
With 34B parameters, Aquila2 34B lands in the range a serious desktop card can handle once the weights are compressed. 132 of the cards we track can run it.
The entry point is the RTX A4500: 20 GB of memory, Q3_K_M compression, roughly 21.5 tokens per second.
The quickest result comes from a B200 at around 99.7 tokens per second — its 8,000 GB/s of bandwidth is what buys that.
Background
Aquila2 34B was published by Beijing Academy of Artificial Intelligence / BAAI, in China, in October 2023. academia is the category the publisher falls under.
It works in Language, and is recorded as doing chat, Language modeling/generation.
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.
Reading the throughput figures
Half the cards that hold it manage more than 21.2 tokens per second, and 103 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.
How it was trained
It was trained on about 2,000,000,000,000 tokens of text.
Step by step
How to choose a GPU for Aquila2 34B
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 Aquila2 34B — around 17.3 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.
-
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 Aquila2 34B stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
Each card runs the least-compressed copy it can hold — Q3_K_M on the smallest card that fits. Setting a floor drops the cards that only manage Aquila2 34B by squeezing it further than you would want.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for Aquila2 34B. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 99.7 tok/s.
-
05
Check the fit verdict before buying
Tight means Aquila2 34B loads and works, with no room to raise the context later. Comfortable means you can. The difference matters more than a few tokens per second.
-
06
Check the card from the other side
Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for Aquila2 34B alone — a card is usually bought for more than one model.
Answers
Aquila2 34B — common questions
How many parameters does Aquila2 34B have?
Aquila2 34B has 34B parameters. 34B safetensors say it is 18.2B params There's also a 70B "experimental" version: https://github.com/FlagAI-Open/Aquila2. 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 Aquila2 34B?
Aquila2 34B was published by Beijing Academy of Artificial Intelligence / BAAI, based in China, categorised as academia.
When was Aquila2 34B released?
Aquila2 34B was published in October 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 Aquila2 34B used for?
Aquila2 34B works in Language, and is recorded as handling chat, Language modeling/generation. These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download Aquila2 34B?
The weights for Aquila2 34B 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 Aquila2 34B 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 Aquila2 34B is rarely worth using — the nearest miss we calculate is short by 6.9 GB. Every figure here assumes the whole model is on the card.
Would two GPUs run Aquila2 34B faster?
Capacity adds across cards; throughput does not. Since 132 of the cards we track already hold Aquila2 34B on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for Aquila2 34B?
A larger card holds a more accurate copy. Across the cards that run Aquila2 34B, 5 compression levels are used; the floor control above pins it to one.
How accurate are these Aquila2 34B speed estimates?
These are estimates with real error bars. The fastest result here, 60–159 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.
What GPU do I need to run Aquila2 34B?
The smallest card in our catalogue that holds Aquila2 34B is the RTX A4500, with 20 GB of memory. It runs the model at Q3_K_M using about 17.3 GB, and produces roughly 21.5 tokens per second. 132 cards in total can run it.
How fast is Aquila2 34B on a GPU?
It depends on the card. The quickest we calculate is a 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 103 of the cards that can run Aquila2 34B clear that.
How much VRAM does Aquila2 34B need?
About 17.3 GB at Q3_K_M 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 Aquila2 34B on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q4_K_M, using about 21.3 GB and generating roughly 38.5 tokens per second — a tight fit.
Is Aquila2 34B open source?
Its weights are published, so Aquila2 34B 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.