Pangu-Weather 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 · 144 tok/s
Fastest card
B200
13,235 tok/s · 180 GB
Which GPUs can run Pangu-Weather?
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 | |||||
|---|---|---|---|---|---|---|---|
|
13,235
tok/s
7,941–21,176 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.0 GB | Q8_0 | Comfortable |
|
13,235
tok/s
7,941–21,176 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.0 GB | Q8_0 | Comfortable |
|
10,569
tok/s
6,341–16,910 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.0 GB | Q8_0 | Comfortable |
|
10,569
tok/s
6,341–16,910 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.0 GB | Q8_0 | Comfortable |
|
8,452
tok/s
5,071–13,524 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
8,090
tok/s
4,854–12,944 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.0 GB | Q8_0 | Comfortable |
|
8,090
tok/s
4,854–12,944 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.0 GB | Q8_0 | Comfortable |
|
7,743
tok/s
4,646–12,388 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.0 GB | Q8_0 | Comfortable |
|
6,872
tok/s
4,123–10,995 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
6,872
tok/s
4,123–10,995 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
6,872
tok/s
4,123–10,995 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.0 GB | Q8_0 | Comfortable |
|
6,518
tok/s
3,911–10,429 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,559
tok/s
3,335–8,894 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,559
tok/s
3,335–8,894 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.0 GB | Q8_0 | Comfortable |
|
5,559
tok/s
3,335–8,894 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,559
tok/s
3,335–8,894 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
5,559
tok/s
3,335–8,894 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.0 GB | Q8_0 | Comfortable |
|
4,233
tok/s
2,540–6,772 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.0 GB | Q8_0 | Comfortable |
|
4,233
tok/s
2,540–6,772 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.0 GB | Q8_0 | Comfortable |
|
3,527
tok/s
2,116–5,644 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
3,452
tok/s
2,071–5,523 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.0 GB | Q8_0 | Comfortable |
|
3,375
tok/s
2,025–5,400 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.0 GB | Q8_0 | Comfortable |
|
3,375
tok/s
2,025–5,400 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.0 GB | Q8_0 | Comfortable |
|
3,375
tok/s
2,025–5,400 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.0 GB | Q8_0 | Comfortable |
|
3,375
tok/s
2,025–5,400 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.0 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
- Huawei
- Organisation type
- Industry
- Country
- China
- Published
- 5 July 2023
- Authors
- Kaifeng Bi, Lingxi Xie, Hengheng Zhang, Xin Chen, Xiaotao Gu, Qi Tian
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Earth science
- Task
- Weather forecasting
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
- 256M
- Training data
- 24,457,821,696,000 tokens
- Epochs
- 100
4*64 million = 256M params "We trained four deep networks with lead times (the time difference between input and output) at 1 h, 3 h, 6 h and 24 h, respectively... This modification increases the number of bias parameters by a factor of 527, with each 3D deep network containing approximately 64 million parameters."
"We used a single point in time for both input and output. The time resolution of the ERA5 data is 1 h; in the training subset (1979–2017), there were as many as 341,880 time points, the amount of training data in one epoch... We fed all included weather variables, including 13 layers of upper-air variables and the surface variables" 341,880 is the number of hours in ~40 years. But there's lots of data for each hour.
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
- 4 × 10²² FLOP
- How it was established
- Hardware
"Each of the four deep networks was trained for 100 epochs, and each of them takes approximately 16 days on a cluster of 192 NVIDIA Tesla-V100 GPUs." 192 * 4 * 16 * 24 * 3600 * 125 teraflops * 0.3 utilization = 3.98e22
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
- 192
- Wall-clock time
- 1,536 hours (64 days)
- Power draw
- 114.6 kW
- Compute cost
- $51,279
4*16 = 64 days "Each of the four deep networks was trained for 100 epochs, andeach of them takes approximately 16 days on a cluster of 192 NVIDIA Tesla-V100 GPUs."
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 (non-commercial)
- Training code
- Unreleased
Models and code here: https://github.com/198808xc/Pangu-Weather Commercial use forbidden
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
- 197
"In meteorology, the Pangu Meteorology Model (or Pangu-Weather) is the first AI model to have surpassed state-of-the-art numerical weather prediction (NWP) methods in terms of accuracy. The prediction speed is also several orders of magnitude faster. In the past, predicting the trajectory of a typhoon over 10 days took 4 to 5 hours of simulation on a high-performance cluster of 3,000 servers. Now, the Pangu model can do it in 10 seconds on a single GPU of a single server, and with more accurate …
Sources
Where this record came from and when it was last checked.
- Reference
- Accurate medium-range global weather forecasting with 3D neural networks
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Pangu-Weather
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 13,235 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 13,235 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 10,569 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 10,569 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 8,452 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 8,090 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 8,090 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 7,743 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 6,872 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 6,872 tok/s
The smallest GPUs that still run Pangu-Weather
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 1.0 GB · Q8_0 · comfortable 159 tok/s
- 02 RTX A400 4 GB · needs 1.0 GB · Q8_0 · comfortable 159 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.0 GB · Q8_0 · comfortable 212 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.0 GB · Q8_0 · comfortable 318 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.0 GB · Q8_0 · comfortable 56.4 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.0 GB · Q8_0 · comfortable 165 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.0 GB · Q8_0 · comfortable 186 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.0 GB · Q8_0 · comfortable 165 tok/s
- 09 Arc A310 4 GB · needs 1.0 GB · Q8_0 · comfortable 133 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.0 GB · Q8_0 · comfortable 138 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
1.0 GB
Fastest
13,235 tok/s
Pangu-Weather reaches a parameter count of 256M. 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 entry point is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 144 tokens per second.
Top of the range is B200, generating roughly 13,235 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Background
Pangu-Weather was published by Huawei, in the country recorded as China, during July 2023. It comes out of an organisation categorised as industry.
It works in the domain of Earth science, and is recorded as performing the task of weather forecasting.
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
The median result is around 371.7 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 818 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.
Without the attention layout on record, the memory column is an approximation. It is close enough to choose hardware by, and least reliable at long context.
What went into building it
Producing it required arithmetic totalling around 4 × 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.
It was trained on a corpus of about 24,457,821,696,000 tokens of text.
Its inclusion criterion: sOTA improvement.
Step by step
How to choose a GPU for Pangu-Weather
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
Start from what it actually needs, which is the requirement of Pangu-Weather, needing around 1.0 GB at a compression of Q8_0. No amount of processing power compensates for a card that cannot hold it.
-
02
Decide how long your conversations run
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 Pangu-Weather.
-
03
Set a quality floor
The quantisation column varies by card, because a bigger card holds a more accurate copy, 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
Compare tokens per second, not specifications
Sort by speed to see how cards rank for Pangu-Weather. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 13,235 tok/s.
-
05
Look at the headroom, not just the fit
Tight means it loads and works with no room to raise the context later, in the case of Pangu-Weather. 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
See what else that card runs
Every card name links to its own page, which runs the same calculation across the whole model catalogue. A card is usually bought for more than one model, so it is worth a look before buying for Pangu-Weather.
Answers
Pangu-Weather — common questions
Pangu-Weather— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 7,941–21,176 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Pangu-Weather— 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 1.0 GB, and produces roughly 144 tokens per second. The number of cards able to run it in total: 818.
Pangu-Weather— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 13,235 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.
Pangu-Weather— how much VRAM does it need?
It needs about 1.0 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.
Pangu-Weather— 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 1.0 GB and generating roughly 2,465 tokens per second. The fit is comfortable.
Pangu-Weather— 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 1.0 GB and generating roughly 1,509 tokens per second. The fit is comfortable.
Pangu-Weather— 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 1.0 GB and generating roughly 1,869 tokens per second. The fit is comfortable.
Pangu-Weather— 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 1.0 GB and generating roughly 2,217 tokens per second. The fit is comfortable.
Pangu-Weather— 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.
Pangu-Weather— how many parameters does it have?
It has a parameter count of 256M. 4*64 million = 256M params "We trained four deep networks with lead times (the time difference between input and output) at 1 h, 3 h, 6 h and 24 h, respectively... This modification increases the number of bias parameters by a factor of 527, with each 3D deep network containing approximately 64 million 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.
Pangu-Weather— who created it?
It was published by Huawei, based in China, an organisation categorised as industry.
Pangu-Weather— when was it released?
It was published in July 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.
Pangu-Weather— what is it used for?
It works in the domain of Earth science, and is recorded as handling the task of weather forecasting. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Pangu-Weather— 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.
Pangu-Weather— how much compute was used to train it?
Training consumed around 4 × 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.
Pangu-Weather— can I run it 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 model is rarely worth using. Every figure here assumes the whole model is resident on the card.
Pangu-Weather— 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.
Pangu-Weather— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
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.