Baize-v2-13B (白泽) TPS calculator

Open weights University of California San Diego,Sun Yat-sen University,Microsoft Research Asia 13B parameters December 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 of 818 cards that can run it

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 Baize-v2-13B (白泽)?

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.

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
University of California San Diego,Sun Yat-sen University,Microsoft Research Asia
Organisation type
Academia,Academia,Industry
Country
United States of America, China
Published
2 December 2023
Authors
Canwen Xu, Daya Guo, Nan Duan, Julian McAuley

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
Base model
LLaMA-13B

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

Total parameters: 13B Trainable parameters: 28M

Training data
tokens

For training the first version of Baize family (Baize v1), we collect a total of 111.5k dialogues through self-chat, using ∼55k questions from each source. This process cost us approximately $100 for calling OpenAI’s API.

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.

How it was established
Hardware
Fine-tuning compute
4.7 × 10¹⁹ FLOP

312000000000000 FLOP/GPU/sec * 140 GPU-hours * 3600 sec / hour * 0.3 [assumed utilization] = 47174400000000000000 FLOP

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
Chip-hours
140

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

The code is released under GPL-3.0. All model weights and data are for research use ONLY. Commercial use is strictly prohibited. We accept NO responsibility or liability for any use of our data, code or weights. https://github.com/project-baize/baize-chatbot cc-by-nc-4.0 https://huggingface.co/project-baize/baize-v2-13b

Hugging Face
project-baize

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
Baize: An Open-Source Chat Model with Parameter-Efficient Tuning on Self-Chat Data
Last updated
11 February 2026

The extremes

What the numbers mean

The hardware side

Minimum card

Xeon Phi 5110P

Memory needed

7.1 GB

Fastest

261 tok/s

Baize-v2-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.

A B200 is the fastest we calculate for it: about 261 tokens per second, from 8,000 GB/s of memory bandwidth.

What this model is

Baize-v2-13B (白泽) was published by University of California San Diego,Sun Yat-sen University,Microsoft Research Asia, in United States of America, in December 2023. It comes out of academia,Academia,Industry.

It works in Language, and is recorded as doing language modeling/generation, Question answering.

Its starting point was LLaMA-13B — most models at this scale are adapted from an existing base rather than built from nothing.

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. It is published under the project-baize organisation on Hugging Face.

What decides the speed

Half the cards that hold it manage more than 21.2 tokens per second, and 459 exceed reading speed outright.

Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.

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.

Step by step

How to choose a GPU for Baize-v2-13B (白泽)

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

  1. 01

    Check what it needs before anything else

    Look at what Baize-v2-13B (白泽) actually needs — around 7.1 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

    The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context Baize-v2-13B (白泽) can slip off a card that handles short questions easily.

  3. 03

    Decide how much compression you will accept

    The quantisation column varies by card, because a bigger card holds a more accurate copy of Baize-v2-13B (白泽) — Q3_K_M on the smallest card that fits. Set a floor to hold the comparison at one level.

  4. 04

    Rank by throughput rather than spec sheet

    Ranking by tokens per second for Baize-v2-13B (白泽) follows memory bandwidth, not core counts, which is why the B200 tops it at 261 tok/s.

  5. 05

    Look at the headroom, not just the fit

    Tight means Baize-v2-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.

  6. 06

    Check the card from the other side

    Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond Baize-v2-13B (白泽).

Answers

Baize-v2-13B (白泽) — common questions

01

What GPU do I need to run Baize-v2-13B (白泽)?

The smallest card in our catalogue that holds Baize-v2-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.

02

How fast is Baize-v2-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 Baize-v2-13B (白泽) clear that.

03

How much VRAM does Baize-v2-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.

04

Can I run Baize-v2-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.

05

Can I run Baize-v2-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.

06

Can I run Baize-v2-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.

07

Can I run Baize-v2-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.

08

Is Baize-v2-13B (白泽) open source?

Its weights are published, so Baize-v2-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.

09

How many parameters does Baize-v2-13B (白泽) have?

Baize-v2-13B (白泽) has 13B parameters. Total parameters: 13B Trainable parameters: 28M. 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.

10

Who created Baize-v2-13B (白泽)?

Baize-v2-13B (白泽) was published by University of California San Diego,Sun Yat-sen University,Microsoft Research Asia, based in United States of America, categorised as academia,Academia,Industry.

11

When was Baize-v2-13B (白泽) released?

Baize-v2-13B (白泽) was published in December 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.

12

What is Baize-v2-13B (白泽) used for?

Baize-v2-13B (白泽) works in Language, and is recorded as handling language modeling/generation, Question answering. These are the areas it was designed around; they describe intent rather than a hard boundary.

13

Where can I download Baize-v2-13B (白泽)?

Its weights are published under the project-baize organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.

14

Can I run Baize-v2-13B (白泽) 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 Baize-v2-13B (白泽) is rarely worth using — the nearest miss we calculate is short by 3.2 GB. Every figure here assumes the whole model is on the card.

15

Would two GPUs run Baize-v2-13B (白泽) faster?

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

16

Why does the quantisation differ between cards for Baize-v2-13B (白泽)?

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

17

How accurate are these Baize-v2-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.

Source

Original publication

Record last updated 11 February 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.