Pangu Pro MoE TPS calculator

Open weights Huawei 72B parameters May 2025

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

61 cards that can run it

818 cards we hold specifications for

Smallest card that fits

A100 PCIe 40 GB

40 GB · Q3_K_M · 24.8 tok/s

Fastest card

B200

47.1 tok/s · 180 GB

Which GPUs can run Pangu Pro MoE?

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.

61 cards match

Calculating
Needs Quantisation Fit
47.1 tok/s

28–75 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 77.8 GB Q8_0 Comfortable
47.1 tok/s

28–75 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 77.8 GB Q8_0 Comfortable
37.6 tok/s

23–60 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 77.8 GB Q8_0 Comfortable
37.6 tok/s

23–60 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 77.8 GB Q8_0 Comfortable
30.1 tok/s

18–48 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 77.8 GB Q8_0 Comfortable
28.8 tok/s

17–46 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 77.8 GB Q8_0 Comfortable
28.8 tok/s

17–46 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 77.8 GB Q8_0 Comfortable
28.7 tok/s

17–46 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 61.0 GB Q6_K Tight
28.7 tok/s

17–46 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 61.0 GB Q6_K Tight
27.5 tok/s

17–44 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 77.8 GB Q8_0 Comfortable
27.0 tok/s

16–43 · low confidence

GRID A100B NVIDIA 48 GB 1,870 GB/s May 2020 40.1 GB IQ4_XS Tight
24.8 tok/s

15–40 · low confidence

A100 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Jun 2020 35.9 GB Q3_K_M Tight
24.8 tok/s

15–40 · low confidence

A100 SXM4 40 GB NVIDIA 40 GB 1,560 GB/s May 2020 35.9 GB Q3_K_M Tight
24.8 tok/s

15–40 · low confidence

A800 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Nov 2022 35.9 GB Q3_K_M Tight
24.4 tok/s

15–39 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 77.8 GB Q8_0 Comfortable
24.4 tok/s

15–39 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 77.8 GB Q8_0 Comfortable
24.4 tok/s

15–39 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 77.8 GB Q8_0 Comfortable
23.2 tok/s

14–37 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 77.8 GB Q8_0 Tight
21.2 tok/s

13–34 · low confidence

H100 SXM5 64 GB NVIDIA 64 GB 2,020 GB/s Mar 2023 52.6 GB Q5_K_M Tight
19.8 tok/s

12–32 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.8 tok/s

12–32 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.8 tok/s

12–32 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.4 tok/s

12–31 · low confidence

RTX PRO 5000 Blackwell NVIDIA 48 GB 1,340 GB/s Mar 2025 40.1 GB IQ4_XS Tight
17.4 tok/s

10–28 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 61.0 GB Q6_K Tight
17.4 tok/s

10–28 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 61.0 GB Q6_K Tight

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
28 May 2025
Authors
Yehui Tang, Xiaosong Li, Fangcheng Liu, Wei Guo, Hang Zhou, Yaoyuan Wang, Kai Han, Xianzhi Yu, Jinpeng Li, Hui Zang, Fei Mi, Xiaojun Meng, Zhicheng Liu, Hanting Chen, Binfan Zheng, Can Chen, Youliang Yan, Ruiming Tang, Peifeng Qin, Xinghao Chen, Dacheng Tao, Yunhe Wang (and Other Contributors)

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Language
Task
Language modeling/generation, Question answering, Quantitative reasoning, Mathematical reasoning, 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
72B

a total of 71.99B parameters and 16.50 billion active parameters

Training data
13,000,000,000,000 tokens

"The pre-training dataset of Pangu Pro MoE contains a total number of 13 trillion tokens produced by our tokenizer with a vocabulary size of 153,376 tokens." "the general phase (9.6T), the reasoning phase (3T), and the annealing phase (0.4T)"

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.3 × 10²⁴ FLOP

6 FLOP / token / parameter * 16.5 * 10^9 active parameters * 13 * 10^12 tokens = 1.287e+24 FLOP

How it was established
Operation counting

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
Huawei Ascend 800T A2
Chips used
4,000
Power draw
2.4 MW

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

CC-BY-4.0 https://gitcode.com/ascend-tribe/pangu-pro-moe

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Record confidence
Confident

Sources

Where this record came from and when it was last checked.

Reference
Pangu Pro MoE: Mixture of Grouped Experts for Efficient Sparsity
Last updated
28 November 2025

The extremes

What the numbers mean

What you need to run it

Minimum card

A100 PCIe 40 GB

Memory needed

35.9 GB

Fastest

47.1 tok/s

Pangu Pro MoE sits at 72B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 61 of the cards we track can hold it.

The least hardware that works is a A100 PCIe 40 GB. Its 40 GB is enough at Q3_K_M compression, giving roughly 24.8 tokens per second.

At the other end, a B200 generates roughly 47.1 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.

Where it came from

Pangu Pro MoE was published by Huawei, in China, in May 2025. industry is the category the publisher falls under.

It works in Language, and is recorded as doing language modeling/generation, Question answering, Quantitative reasoning, Mathematical reasoning, Code 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.

Understanding the speeds

Across every card that can run it, the middle of the range is about 16.6 tokens per second, and 51 of them clear the ten tokens per second that roughly matches reading speed.

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.

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.3 × 10²⁴ FLOP, on Huawei Ascend 800T A2. That figure describes the cost of creating it and has no bearing on how quickly it generates text.

It was trained on about 13,000,000,000,000 tokens of text.

Step by step

How to choose a GPU for Pangu Pro MoE

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Read the memory figure first

    Look at what Pangu Pro MoE actually needs — around 35.9 GB at Q3_K_M. No amount of processing power compensates for a card that cannot hold it.

  2. 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 Pangu Pro MoE stops fitting a card that seemed fine.

  3. 03

    Set a quality floor

    Compression is what makes Pangu Pro MoE fit smaller cards, at some cost in accuracy — Q3_K_M on the smallest card that fits. A minimum quality removes the ones that go too far.

  4. 04

    Rank by throughput rather than spec sheet

    Sort by speed to see how cards rank for Pangu Pro MoE. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 47.1 tok/s.

  5. 05

    Look at the headroom, not just the fit

    Tight means Pangu Pro MoE 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.

  6. 06

    See what else that card runs

    Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond Pangu Pro MoE.

Answers

Pangu Pro MoE — common questions

01

Where can I download Pangu Pro MoE?

The weights for Pangu Pro MoE are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

02

How much compute was used to train Pangu Pro MoE?

Around 1.3 × 10²⁴ FLOP, on Huawei Ascend 800T A2. 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.

03

Can I run Pangu Pro MoE 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 15.5 GB. Our figures for Pangu Pro MoE assume it is fully resident.

04

Would two GPUs run Pangu Pro MoE faster?

A second card roughly doubles the memory available but not the generation rate. With 61 cards already able to run Pangu Pro MoE alone, the case for pairing is weak.

05

Why does the quantisation differ between cards for Pangu Pro MoE?

Each card is shown running the least-compressed copy it can hold, and Pangu Pro MoE appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.

06

How accurate are these Pangu Pro MoE 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 28–75 tok/s on the B200 rather than a single number.

07

What GPU do I need to run Pangu Pro MoE?

The smallest card in our catalogue that holds Pangu Pro MoE is the A100 PCIe 40 GB, with 40 GB of memory. It runs the model at Q3_K_M using about 35.9 GB, and produces roughly 24.8 tokens per second. 61 cards in total can run it.

08

How fast is Pangu Pro MoE on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 47.1 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 51 of the cards that can run Pangu Pro MoE clear that.

09

How much VRAM does Pangu Pro MoE need?

About 35.9 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.

10

Is Pangu Pro MoE open source?

Its weights are published, so Pangu Pro MoE 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.

11

How many parameters does Pangu Pro MoE have?

Pangu Pro MoE has 72B parameters. a total of 71.99B parameters and 16.50 billion active 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.

12

Who created Pangu Pro MoE?

Pangu Pro MoE was published by Huawei, based in China, categorised as industry.

13

When was Pangu Pro MoE released?

Pangu Pro MoE was published in May 2025.

14

What is Pangu Pro MoE used for?

Pangu Pro MoE works in Language, and is recorded as handling language modeling/generation, Question answering, Quantitative reasoning, Mathematical reasoning, Code generation. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.

Source

Original publication

Record last updated 28 November 2025

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.