Zidong Taichu 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
Tesla C1080
4 GB · Q6_K · 16.7 tok/s
Fastest card
B200
1,059 tok/s · 180 GB
Which GPUs can run Zidong Taichu?
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.
818 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
1,059
tok/s
635–1,694 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 4.1 GB | Q8_0 | Comfortable |
|
1,059
tok/s
635–1,694 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 4.1 GB | Q8_0 | Comfortable |
|
846
tok/s
507–1,353 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 4.1 GB | Q8_0 | Comfortable |
|
846
tok/s
507–1,353 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 4.1 GB | Q8_0 | Comfortable |
|
676
tok/s
406–1,082 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 4.1 GB | Q8_0 | Comfortable |
|
647
tok/s
388–1,036 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 4.1 GB | Q8_0 | Comfortable |
|
647
tok/s
388–1,036 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 4.1 GB | Q8_0 | Comfortable |
|
619
tok/s
372–991 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 4.1 GB | Q8_0 | Comfortable |
|
550
tok/s
330–880 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 4.1 GB | Q8_0 | Comfortable |
|
550
tok/s
330–880 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 4.1 GB | Q8_0 | Comfortable |
|
550
tok/s
330–880 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 4.1 GB | Q8_0 | Comfortable |
|
521
tok/s
313–834 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 4.1 GB | Q8_0 | Comfortable |
|
445
tok/s
267–712 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 4.1 GB | Q8_0 | Comfortable |
|
445
tok/s
267–712 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 4.1 GB | Q8_0 | Comfortable |
|
445
tok/s
267–712 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 4.1 GB | Q8_0 | Comfortable |
|
445
tok/s
267–712 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 4.1 GB | Q8_0 | Comfortable |
|
445
tok/s
267–712 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 4.1 GB | Q8_0 | Comfortable |
|
339
tok/s
203–542 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 4.1 GB | Q8_0 | Comfortable |
|
339
tok/s
203–542 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 4.1 GB | Q8_0 | Comfortable |
|
282
tok/s
169–451 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 4.1 GB | Q8_0 | Comfortable |
|
276
tok/s
166–442 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 4.1 GB | Q8_0 | Comfortable |
|
270
tok/s
162–432 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 4.1 GB | Q8_0 | Comfortable |
|
270
tok/s
162–432 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 4.1 GB | Q8_0 | Comfortable |
|
270
tok/s
162–432 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 4.1 GB | Q8_0 | Comfortable |
|
270
tok/s
162–432 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 4.1 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
- Chinese Academy of Sciences,Wuhan AI Computing Center
- Organisation type
- Academia,Government
- Country
- China
- Published
- 11 August 2021
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Multimodal, Speech, Vision, Language
- Task
- Language modeling/generation, Speech recognition (ASR), Image captioning
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
- 3.2B
- Training data
- tokens
共32亿参数 translated as A total of 3.2 billion parameters
主要采用CLUE与WMT中收集的中文数据,同时我们加入了额外收集的对话数据以及翻译平行语料中的中文部分,总共约250G的中文语料,领域覆盖广泛。 From context, seems to mean 250GB 250GB * 167M tokens/GB = 4.175e+10 tokens https://gitee.com/zidongtaichu/multi-modal-models/tree/master/text#%E6%95%B0%E6%8D%AE%E9%9B%86
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
- 8 × 10²⁰ FLOP
- How it was established
- Operation counting
4.175e10 * 3.2e9 * 6 = 8.016e20 FLOP
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
Apache 2.0 https://gitee.com/zidongtaichu/multi-modal-models I don't see training code there
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Why it is tracked
- Historical significance
- Record confidence
- Confident
The world’s first image, language, and audio trimodal pre-trained model.
Sources
Where this record came from and when it was last checked.
- Reference
- Zidong Ancestral multi-modal large model
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Zidong Taichu
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 B300 288 GB · 8,000 GB/s · Q8_0 1,059 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 1,059 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 846 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 846 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 676 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 647 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 647 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 619 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 550 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 550 tok/s
The smallest GPUs that still run Zidong Taichu
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 3.4 GB · Q6_K · tight 18.5 tok/s
- 02 RTX A400 4 GB · needs 3.4 GB · Q6_K · tight 18.5 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 3.4 GB · Q6_K · tight 24.6 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 3.4 GB · Q6_K · tight 36.9 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 3.4 GB · Q6_K · tight 6.6 tok/s
- 06 Radeon RX 6450M 4 GB · needs 3.4 GB · Q6_K · tight 19.2 tok/s
- 07 Radeon RX 6550M 4 GB · needs 3.4 GB · Q6_K · tight 21.6 tok/s
- 08 Radeon RX 6550S 4 GB · needs 3.4 GB · Q6_K · tight 19.2 tok/s
- 09 Arc A310 4 GB · needs 3.4 GB · Q6_K · tight 15.5 tok/s
- 10 Arc Pro A30M 4 GB · needs 3.4 GB · Q6_K · tight 16.0 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
3.4 GB
Fastest
1,059 tok/s
Zidong Taichu reaches a parameter count of 3.2B. 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: 818.
The entry point is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q6_K and producing around 16.7 tokens per second.
At the other end sits B200, generating roughly 1,059 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
What this model is
Zidong Taichu was published by Chinese Academy of Sciences,Wuhan AI Computing Center, in the country recorded as China, during August 2021. The publishing organisation is categorised as academia,Government.
It works in the domain of Multimodal, Speech, Vision, Language, and is recorded as performing the task of language modeling/generation, Speech recognition (ASR), Image captioning.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.
What decides the speed
Half the cards that hold it manage more than 33.6 tokens per second. Exceeding reading speed outright: 779 of them.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
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
Training it took a computation budget of roughly 8 × 10²⁰ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The reason it appears in this catalogue at all: historical significance.
Step by step
How to choose a GPU for Zidong Taichu
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Read the memory figure first
Every card here has been checked against Zidong Taichu, needing around 3.4 GB at a compression of Q6_K. Capacity is the gate — a card either holds it or it does not.
-
02
Decide how long your conversations run
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 Zidong Taichu.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold, reaching a compression of Q6_K 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 Zidong Taichu. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 1,059 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs, but leaves nothing spare for a longer conversation, in the case of Zidong Taichu. 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 Zidong Taichu.
Answers
Zidong Taichu — common questions
Zidong Taichu— how many parameters does it have?
It has a parameter count of 3.2B. 共32亿参数 translated as A total of 3.2 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.
Zidong Taichu— who created it?
It was published by Chinese Academy of Sciences,Wuhan AI Computing Center, based in China, an organisation categorised as academia,Government.
Zidong Taichu— when was it released?
It was published in August 2021. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
Zidong Taichu— what is it used for?
It works in the domain of Multimodal, Speech, Vision, Language, and is recorded as handling the task of language modeling/generation, Speech recognition (ASR), Image captioning. These are the areas it was designed around; they describe intent rather than a hard boundary.
Zidong Taichu— 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.
Zidong Taichu— how much compute was used to train it?
Training consumed around 8 × 10²⁰ FLOP. 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.
Zidong Taichu— 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. Every figure here assumes the whole model is resident on the card.
Zidong Taichu— would two GPUs run it faster?
Capacity adds across cards; throughput does not. The number of cards already holding it on their own: 818. So a second card is rarely the answer here.
Zidong Taichu— 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: 2. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Zidong Taichu— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 635–1,694 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Zidong Taichu— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Tesla C1080, with a memory capacity of 4 GB. It runs the model at a compression of Q6_K using about 3.4 GB, and produces roughly 16.7 tokens per second. The number of cards able to run it in total: 818.
Zidong Taichu— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 1,059 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: 779.
Zidong Taichu— how much VRAM does it need?
It needs about 3.4 GB at a compression of Q6_K, 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.
Zidong Taichu— 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 Q8_0, using about 4.1 GB and generating roughly 197 tokens per second. The fit is comfortable.
Zidong Taichu— 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 Q8_0, using about 4.1 GB and generating roughly 121 tokens per second. The fit is comfortable.
Zidong Taichu— 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 Q8_0, using about 4.1 GB and generating roughly 150 tokens per second. The fit is comfortable.
Zidong Taichu— 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 4.1 GB and generating roughly 177 tokens per second. The fit is comfortable.
Zidong Taichu— 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.
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.