GLM-130B 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 PRO 5000 72 GB Blackwell
72 GB · Q3_K_M · 11.8 tok/s
Fastest card
H100 NVL 94 GB
29.6 tok/s · 94 GB
Which GPUs can run GLM-130B?
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.
38 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
29.6
tok/s
18–47 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 79.3 GB | Q4_K_M | Tight |
|
26.9
tok/s
16–43 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 71.8 GB | IQ4_XS | Tight |
|
26.9
tok/s
16–43 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 71.8 GB | IQ4_XS | Tight |
|
26.1
tok/s
16–42 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 139.9 GB | Q8_0 | Tight |
|
26.1
tok/s
16–42 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 139.9 GB | Q8_0 | Comfortable |
|
25.3
tok/s
15–40 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 79.3 GB | Q4_K_M | Tight |
|
25.3
tok/s
15–40 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 79.3 GB | Q4_K_M | Tight |
|
25.3
tok/s
15–40 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 79.3 GB | Q4_K_M | Tight |
|
24.2
tok/s
15–39 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 109.6 GB | Q6_K | Tight |
|
23.2
tok/s
14–37 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 109.6 GB | Q6_K | Tight |
|
23.2
tok/s
14–37 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 109.6 GB | Q6_K | Tight |
|
20.8
tok/s
12–33 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 139.9 GB | Q8_0 | Comfortable |
|
20.8
tok/s
12–33 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 139.9 GB | Q8_0 | Comfortable |
|
19.7
tok/s
12–31 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 109.6 GB | Q6_K | Tight |
|
16.3
tok/s
10–26 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 71.8 GB | IQ4_XS | Tight |
|
16.3
tok/s
10–26 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 71.8 GB | IQ4_XS | Tight |
|
16.3
tok/s
10–26 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 71.8 GB | IQ4_XS | Tight |
|
16.3
tok/s
10–26 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 71.8 GB | IQ4_XS | Tight |
|
16.3
tok/s
10–26 · low confidence |
H100 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Oct 2022 | 71.8 GB | IQ4_XS | Tight |
|
16.3
tok/s
10–26 · low confidence |
H800 PCIe 80 GB NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 71.8 GB | IQ4_XS | Tight |
|
15.5
tok/s
9–25 · low confidence |
A100 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Jun 2021 | 71.8 GB | IQ4_XS | Tight |
|
15.5
tok/s
9–25 · low confidence |
A800 PCIe 80 GB NVIDIA | 80 GB | 1,940 GB/s | Nov 2022 | 71.8 GB | IQ4_XS | Tight |
|
15.3
tok/s
9–24 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 139.9 GB | Q8_0 | Comfortable |
|
13.5
tok/s
8–22 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 139.9 GB | Q8_0 | Comfortable |
|
13.5
tok/s
8–22 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 139.9 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
- Tsinghua University
- Organisation type
- Academia
- Country
- China
- Published
- 4 August 2022
- Authors
- Aohan Zeng, Xiao Liu, Zhengxiao Du, Zihan Wang, Hanyu Lai, Ming Ding, Zhuoyi Yang, Yifan Xu, Wendi Zheng, Xiao Xia, Weng Lam Tam, Zixuan Ma, Yufei Xue, Jidong Zhai, Wenguang Chen, Peng Zhang, Yuxiao Dong, Jie Tang
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
- 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
- 130B
- Training data
- 152,000,000,000 tokens
- Epochs
- 1
- Batch size
- 8,650,752
Dense model
400B "We completed the 400B-token training and evaluation of GLM-130B in July, and subsequently released the model and pre-training details in August 2022. " from https://arxiv.org/pdf/2406.12793 "As of July 3rd, 2022, GLM-130B has been trained on over 400 billion text tokens (200B each for Chinese and English)"
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
- 3.5 × 10²³ FLOP
- How it was established
- Operation counting,Hardware
"96 NVIDIA A100 (40G * 8) servers for 2 months" 312 TFLOPS/GPU * 96 servers * 8 GPU/server * 2 months * 32.5% utilization = 4.037e23 utilization rate - citation from the paper: "we report hardware FLOPs utilization (HFU) of 43.3% and model FLOPs utilization (MFU) of 32.5% due to re-materialization." Aligns pretty well with 6ND: 6 * 400B * 130B = 3.12E23 Geometric mean: sqrt(4.037e23 * 3.12e23) = 3.549e23
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
- 768
- Chip-hours
- 1,105,920
- Wall-clock time
- 1,440 hours (60 days)
- Hardware utilisation
- MFU 32.5% · HFU 43.3%
- Power draw
- 615.7 kW
- Compute cost
- $820,297
"During the 60-day access to the cluster, we manage to train GLM-130B for 400 billion tokens" 60 days * 24 = 1,440 hours
"Following the calculation in (Chowdhery et al., 2022), we report hardware FLOPs utilization (HFU) of 43.3% and model FLOPs utilization (MFU) of 32.5% due to re-materialization."
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
non commercial license. looks like inference but not training code: https://github.com/THUDM/GLM-130B/blob/main/MODEL_LICENSE
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Foundation model
- Yes
- Likely above 10²³ FLOP
- Yes
- Why it is tracked
- SOTA improvement
- Record confidence
- Confident
- Citations
- 1,264
- Benchmark data
- GLM-130B
"GLM-130B achieves an accuracy of 80.2% on zero-shot LAMBADA (En), while 76.2% for GPT-3 175B and 77.9% for the SOTA offered by PaLM 540B." "We compare GLM-130B to the largest existing Chinese monolingual language model—the 260B ERNIE Titan 3.0 (Wang et al., 2021). <..> GLM-130B consistently outperforms ERNIE Titan 3.0 across 12 tasks (Cf. Figure 8)."
Sources
Where this record came from and when it was last checked.
- Reference
- GLM-130B: An Open Bilingual Pre-trained Model
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run GLM-130B
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 H100 NVL 94 GB 94 GB · 3,940 GB/s · Q4_K_M 29.6 tok/s
- 02 H800 SXM5 80 GB · 3,360 GB/s · IQ4_XS 26.9 tok/s
- 03 H100 SXM5 80 GB 80 GB · 3,360 GB/s · IQ4_XS 26.9 tok/s
- 04 B300 288 GB · 8,000 GB/s · Q8_0 26.1 tok/s
- 05 B200 180 GB · 8,000 GB/s · Q8_0 26.1 tok/s
- 06 H100 PCIe 96 GB 96 GB · 3,360 GB/s · Q4_K_M 25.3 tok/s
- 07 H100 SXM5 94 GB 94 GB · 3,360 GB/s · Q4_K_M 25.3 tok/s
- 08 H100 SXM5 96 GB 96 GB · 3,360 GB/s · Q4_K_M 25.3 tok/s
- 09 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q6_K 24.2 tok/s
- 10 H200 NVL 141 GB · 4,890 GB/s · Q6_K 23.2 tok/s
The smallest GPUs that still run GLM-130B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 RTX PRO 5000 72 GB Blackwell 72 GB · needs 64.2 GB · Q3_K_M · tight 11.8 tok/s
- 02 H100 CNX 80 GB · needs 71.8 GB · IQ4_XS · tight 16.3 tok/s
- 03 H800 PCIe 80 GB 80 GB · needs 71.8 GB · IQ4_XS · tight 16.3 tok/s
- 04 H800 SXM5 80 GB · needs 71.8 GB · IQ4_XS · tight 26.9 tok/s
- 05 A800 PCIe 80 GB 80 GB · needs 71.8 GB · IQ4_XS · tight 15.5 tok/s
- 06 H100 PCIe 80 GB 80 GB · needs 71.8 GB · IQ4_XS · tight 16.3 tok/s
- 07 H100 SXM5 80 GB 80 GB · needs 71.8 GB · IQ4_XS · tight 26.9 tok/s
- 08 A800 SXM4 80 GB 80 GB · needs 71.8 GB · IQ4_XS · tight 16.3 tok/s
- 09 A100 PCIe 80 GB 80 GB · needs 71.8 GB · IQ4_XS · tight 15.5 tok/s
- 10 A100X 80 GB · needs 71.8 GB · IQ4_XS · tight 16.3 tok/s
What the numbers mean
The hardware side
Minimum card
RTX PRO 5000 72 GB Blackwell
Memory needed
64.2 GB
Fastest
29.6 tok/s
GLM-130B sits at 130B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 38 of the cards we track can hold it.
At the low end, a RTX PRO 5000 72 GB Blackwell handles it — 72 GB, at Q3_K_M, for about 11.8 tokens per second.
The quickest result comes from a H100 NVL 94 GB at around 29.6 tokens per second — its 3,940 GB/s of bandwidth is what buys that.
About this model
GLM-130B was published by Tsinghua University, in China, in August 2022. academia is the category the publisher falls under.
It works in Language, and is recorded as doing language modeling/generation, Translation.
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.
How fast it runs, and why
Half the cards that hold it manage more than 16.3 tokens per second, and 35 exceed reading speed outright.
Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.
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.
What went into building it
The training run consumed about 3.5 × 10²³ FLOP, on NVIDIA A100 SXM4 40 GB. That figure describes the cost of creating it and has no bearing on how quickly it generates text.
Around 152,000,000,000 tokens went into training it.
It is tracked in the underlying dataset for one reason in particular: sOTA improvement.
Step by step
How to choose a GPU for GLM-130B
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
Every card here has been checked against GLM-130B — around 64.2 GB at 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 GLM-130B stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
Compression is what makes GLM-130B 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.
-
04
Rank by throughput rather than spec sheet
The speed ordering for GLM-130B is effectively an ordering by memory bandwidth, which is why the H100 NVL 94 GB tops it at 29.6 tok/s.
-
05
Read the fit column last
A tight fit runs GLM-130B but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
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. Worth a look before buying for GLM-130B alone — a card is usually bought for more than one model.
Answers
GLM-130B — common questions
How many parameters does GLM-130B have?
GLM-130B has 130B parameters. Dense model. 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 GLM-130B?
GLM-130B was published by Tsinghua University, based in China, categorised as academia.
When was GLM-130B released?
GLM-130B was published in August 2022. 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 GLM-130B used for?
GLM-130B works in Language, and is recorded as handling language modeling/generation, Translation. 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.
Where can I download GLM-130B?
The weights for GLM-130B are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train GLM-130B?
Around 3.5 × 10²³ FLOP, on NVIDIA A100 SXM4 40 GB. 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.
Can I run GLM-130B 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 GLM-130B is rarely worth using — the nearest miss we calculate is short by 21.7 GB. Every figure here assumes the whole model is on the card.
Would two GPUs run GLM-130B faster?
Two cards buy memory rather than speed. That matters for GLM-130B only if one card cannot hold it — 38 can, so a second adds little.
Why does the quantisation differ between cards for GLM-130B?
Each card is shown running the least-compressed copy it can hold, and GLM-130B appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these GLM-130B speed estimates?
These are estimates with real error bars. The fastest result here, 18–47 tok/s on the H100 NVL 94 GB, could reasonably land anywhere in its published range depending on which runtime you use.
What GPU do I need to run GLM-130B?
The smallest card in our catalogue that holds GLM-130B is the RTX PRO 5000 72 GB Blackwell, with 72 GB of memory. It runs the model at Q3_K_M using about 64.2 GB, and produces roughly 11.8 tokens per second. 38 cards in total can run it.
How fast is GLM-130B on a GPU?
It depends on the card. The quickest we calculate is a H100 NVL 94 GB at about 29.6 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 35 of the cards that can run GLM-130B clear that.
How much VRAM does GLM-130B need?
About 64.2 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.
Is GLM-130B open source?
Its weights are published, so GLM-130B 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.