CodeGeeX TPS calculator

Open weights Z.ai (Zhipu AI),Tsinghua University 13B parameters June 2022

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

509 cards that can run it

818 cards we hold specifications for

Smallest card that fits

Xeon Phi 5110P

8 GB · Q3_K_M · 18.3 tok/s

Fastest card

B200

261 tok/s · 180 GB

Which GPUs can run CodeGeeX?

Set the inputs, read the answer

Context length tokens

A longer conversation needs more memory, which can push this model off smaller cards.

Minimum quality

Hides cards that would only fit the model by compressing it below this point.

Search cards

Card memory

Also show cards that cannot run it

509 cards match

Calculating

					Needs	Quantisation	Fit
261 tok/s 156–417 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	14.6 GB	Q8_0	Comfortable
261 tok/s 156–417 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	14.6 GB	Q8_0	Comfortable
208 tok/s 125–333 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	14.6 GB	Q8_0	Comfortable
208 tok/s 125–333 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	14.6 GB	Q8_0	Comfortable
166 tok/s 100–266 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	14.6 GB	Q8_0	Comfortable
159 tok/s 96–255 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	14.6 GB	Q8_0	Comfortable
159 tok/s 96–255 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	14.6 GB	Q8_0	Comfortable
152 tok/s 91–244 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	14.6 GB	Q8_0	Comfortable
135 tok/s 81–217 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	14.6 GB	Q8_0	Comfortable
135 tok/s 81–217 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	14.6 GB	Q8_0	Comfortable
135 tok/s 81–217 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	14.6 GB	Q8_0	Comfortable
131 tok/s 79–210 · low confidence	CMP 170HX 8 GB NVIDIA	8 GB	1,490 GB/s	Sep 2021	7.1 GB	Q3_K_M	Tight
128 tok/s 77–205 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	14.6 GB	Q8_0	Comfortable
117 tok/s 70–188 · low confidence	CMP 170HX 10 GB NVIDIA	10 GB	1,560 GB/s	Sep 2021	8.6 GB	Q4_K_M	Tight
109 tok/s 66–175 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	14.6 GB	Q8_0	Comfortable
109 tok/s 66–175 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	14.6 GB	Q8_0	Comfortable
109 tok/s 66–175 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	14.6 GB	Q8_0	Comfortable
109 tok/s 66–175 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	14.6 GB	Q8_0	Comfortable
109 tok/s 66–175 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	14.6 GB	Q8_0	Comfortable
83.4 tok/s 50–133 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	14.6 GB	Q8_0	Comfortable
83.4 tok/s 50–133 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	14.6 GB	Q8_0	Comfortable
69.5 tok/s 42–111 · low confidence	Data Center GPU Max 1550 Intel	128 GB	3,280 GB/s	Jan 2023	14.6 GB	Q8_0	Comfortable
68.0 tok/s 41–109 · low confidence	Data Center GPU Max Subsystem Intel	128 GB	3,210 GB/s	Jan 2023	14.6 GB	Q8_0	Comfortable
67.5 tok/s 41–108 · low confidence	RTX A5000-8Q NVIDIA	8 GB	768 GB/s	Apr 2021	7.1 GB	Q3_K_M	Tight
66.5 tok/s 40–106 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	14.6 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: Z.ai (Zhipu AI),Tsinghua University
Organisation type: Industry,Academia
Country: China
Published: 22 June 2022

What it does

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

Domain: Language
Task: Code generation
Approach: Self-supervised learning

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: 13B
Training data: 850,000,000,000 tokens
Batch size: 6,291,456

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.6 × 10²² 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 910
Wall-clock time: 156 hours

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: Open source

How it is classified

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

Foundation model: Yes
Record confidence: Confident

Sources

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

Last updated: 28 November 2025

The extremes

The ten fastest GPUs that run CodeGeeX

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.

The smallest GPUs that still run CodeGeeX

The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.

What the numbers mean

What it takes to run this model

Minimum card

Xeon Phi 5110P

Memory needed

7.1 GB

Fastest

261 tok/s

CodeGeeX reaches a parameter count of 13B. 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: 509.

The smallest card that holds it is Xeon Phi 5110P, with a memory capacity of 8 GB, running it at a compression of Q3_K_M and producing around 18.3 tokens per second.

Top of the range is B200, generating roughly 261 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

Where it came from

CodeGeeX was published by Z.ai (Zhipu AI),Tsinghua University, in the country recorded as China, during June 2022. The publishing organisation is categorised as industry,Academia.

It works in the domain of Language, and is recorded as performing the task of code generation.

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.

Understanding the speeds

The median result is around 21.2 tokens per second. Producing text faster than most people read it: 459 of them.

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 6.6 × 10²² FLOP, on hardware recorded as Huawei Ascend 910. That figure measures what producing the model cost, and has no bearing on how fast it answers.

Training consumed a corpus of around 850,000,000,000 tokens of text.

Step by step

How to choose a GPU for CodeGeeX

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

The table lists every card able to hold CodeGeeX, needing around 7.1 GB at a compression of Q3_K_M. That figure, not the headline performance of a card, 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 a card that seemed fine stops fitting CodeGeeX.
03

Set a quality floor

Compression is what makes a model fit smaller cards, at some cost in accuracy, 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

Ranking by tokens per second follows memory bandwidth rather than core counts, for CodeGeeX. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 261 tok/s.
05

Look at the headroom, not just the fit

A tight fit runs, but leaves nothing spare for a longer conversation, in the case of CodeGeeX. 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

Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond CodeGeeX.

Answers

CodeGeeX — common questions

CodeGeeX— how much VRAM does it need?

It needs about 7.1 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.

CodeGeeX— 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 Q3_K_M, using about 7.1 GB and generating roughly 131 tokens per second. The fit is tight.

CodeGeeX— 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 Q5_K_M, using about 10.1 GB and generating roughly 53.1 tokens per second. The fit is tight.

CodeGeeX— 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 Q6_K, using about 11.6 GB and generating roughly 53.5 tokens per second. The fit is comfortable.

CodeGeeX— 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 14.6 GB and generating roughly 43.7 tokens per second. The fit is comfortable.

CodeGeeX— 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.

CodeGeeX— how many parameters does it have?

It has a parameter count of 13B. "We introduce CodeGeeX, a large-scale multilingual code generation model with 13 billion 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.

CodeGeeX— who created it?

It was published by Z.ai (Zhipu AI),Tsinghua University, based in China, an organisation categorised as industry,Academia.

CodeGeeX— when was it released?

It was published in June 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.

CodeGeeX— what is it used for?

It works in the domain of Language, and is recorded as handling the task of code generation. These are the areas it was designed around; they describe intent rather than a hard boundary.

CodeGeeX— 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.

CodeGeeX— how much compute was used to train it?

Training consumed around 6.6 × 10²² FLOP, on hardware recorded as Huawei Ascend 910. 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.

CodeGeeX— 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 3.2 GB. Every figure here assumes the whole model is resident on the card.

CodeGeeX— 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: 509. So a second card is rarely the answer here.

CodeGeeX— why does the quantisation differ between cards?

Because capacity varies, so does how hard it has to be squeezed. The number of distinct levels in the table above: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

CodeGeeX— how accurate are these speed estimates?

They are calculated from specifications rather than measured, and each carries a range. One example: 156–417 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

CodeGeeX— what GPU do I need to run it?

The smallest card in our catalogue that holds it is Xeon Phi 5110P, with a memory capacity of 8 GB. It runs the model at a compression of Q3_K_M using about 7.1 GB, and produces roughly 18.3 tokens per second. The number of cards able to run it in total: 509.

CodeGeeX— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 261 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: 459.

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.

All AI models