CodeFuse-13B TPS calculator

Open weights Ant Group 13B parameters October 2023

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 CodeFuse-13B?

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: Ant Group
Organisation type: Industry
Country: China
Published: 10 October 2023
Authors: Peng Di, Jianguo Li, Hang Yu, Wei Jiang, Wenting Cai, Yang Cao, Chaoyu Chen, Dajun Chen, Hongwei Chen, Liang Chen, Gang Fan, Jie Gong, Zi Gong, Wen Hu, Tingting Guo, Zhichao Lei, Ting Li, Zheng Li, Ming Liang, Cong Liao, Bingchang Liu, Jiachen Liu, Zhiwei Liu, Shaojun Lu, Min Shen, Guangpei Wang, Huan Wang, Zhi Wang, Zhaogui Xu, Jiawei Yang, Qing Ye, Gehao Zhang, Yu Zhang, Zelin Zhao, Xunjin Zheng…

What it does

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

Domain: Language
Task: 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: 13B
Training data: 1,000,000,000,000 tokens
Batch size: 16,777,216

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.1 × 10²³ FLOP
How it was established: Hardware

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 80 GB
Chips used: 512
Wall-clock time: 960 hours (40 days)
Hardware utilisation: HFU 57.7%
Power draw: 406.6 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: Unreleased

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: Confident
Citations: 29

Sources

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

Reference: CodeFuse-13B: A Pretrained Multi-lingual Code Large Language Model
Last updated: 25 May 2026

The extremes

The ten fastest GPUs that run CodeFuse-13B

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 CodeFuse-13B

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

The hardware side

Minimum card

Xeon Phi 5110P

Memory needed

7.1 GB

Fastest

261 tok/s

CodeFuse-13B is small enough at 13B parameters that hardware is rarely the obstacle — 509 of the cards we track can run it, including cards several years old.

At the low end, a Xeon Phi 5110P handles it — 8 GB, at Q3_K_M, for about 18.3 tokens per second.

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

Where it came from

CodeFuse-13B was published by Ant Group, in China, in October 2023. industry is the category the publisher falls under.

It works in Language, and is recorded as doing code generation.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.

Understanding the speeds

The median result is around 21.2 tokens per second; 459 cards produce text faster than most people read it.

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.

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.

How it was trained

Training it took roughly 3.1 × 10²³ FLOP of computation, on NVIDIA A100 SXM4 80 GB — a measure of what producing the model cost, not of how fast it answers.

The training set ran to roughly 1,000,000,000,000 tokens.

Step by step

How to choose a GPU for CodeFuse-13B

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

The table lists every card that can hold CodeFuse-13B — around 7.1 GB at Q3_K_M. That figure, not the card's headline performance, is what decides whether it runs.
02

Decide how long your conversations run

Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for CodeFuse-13B.
03

Decide how much compression you will accept

Compression is what makes CodeFuse-13B 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

Sort by speed

Ranking by tokens per second for CodeFuse-13B follows memory bandwidth, not core counts, which is why the B200 tops it at 261 tok/s.
05

Read the fit column last

Tight means CodeFuse-13B 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

Open the card you have settled on

Following a card through to its own page shows every other model it can hold, which is the question that follows once CodeFuse-13B is settled.

Answers

CodeFuse-13B — common questions

Is CodeFuse-13B open source?

Its weights are published, so CodeFuse-13B 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.

How many parameters does CodeFuse-13B have?

CodeFuse-13B has 13B 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.

Who created CodeFuse-13B?

CodeFuse-13B was published by Ant Group, based in China, categorised as industry.

When was CodeFuse-13B released?

CodeFuse-13B 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 CodeFuse-13B used for?

CodeFuse-13B works in Language, and is recorded as handling 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.

Where can I download CodeFuse-13B?

The weights for CodeFuse-13B 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 CodeFuse-13B?

Around 3.1 × 10²³ FLOP, on NVIDIA A100 SXM4 80 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 CodeFuse-13B 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 3.2 GB. Our figures for CodeFuse-13B assume it is fully resident.

Would two GPUs run CodeFuse-13B faster?

Capacity adds across cards; throughput does not. Since 509 of the cards we track already hold CodeFuse-13B on their own, a second card is rarely the answer here.

Why does the quantisation differ between cards for CodeFuse-13B?

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

How accurate are these CodeFuse-13B speed estimates?

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

What GPU do I need to run CodeFuse-13B?

The smallest card in our catalogue that holds CodeFuse-13B is the Xeon Phi 5110P, with 8 GB of memory. It runs the model at Q3_K_M using about 7.1 GB, and produces roughly 18.3 tokens per second. 509 cards in total can run it.

How fast is CodeFuse-13B on a GPU?

It depends on the card. The quickest we calculate is a 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 459 of the cards that can run CodeFuse-13B clear that.

How much VRAM does CodeFuse-13B need?

About 7.1 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 CodeFuse-13B on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q3_K_M, using about 7.1 GB and generating roughly 131 tokens per second — a tight fit.

Can I run CodeFuse-13B on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q5_K_M, using about 10.1 GB and generating roughly 53.1 tokens per second — a tight fit.

Can I run CodeFuse-13B on a 16 GB GPU?

Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q6_K, using about 11.6 GB and generating roughly 53.5 tokens per second — a comfortable fit.

Can I run CodeFuse-13B on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 14.6 GB and generating roughly 43.7 tokens per second — a comfortable fit.

Source

Original publication

Record last updated 25 May 2026

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