OmniGen TPS calculator

Open weights Beijing Academy of Artificial Intelligence / BAAI 3.8B parameters September 2024

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 that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla C1080

4 GB · Q5_K_M · 17.3 tok/s

Fastest card

B200

892 tok/s · 180 GB

Which GPUs can run OmniGen?

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
892 tok/s

535–1,427 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 4.8 GB Q8_0 Comfortable
892 tok/s

535–1,427 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 4.8 GB Q8_0 Comfortable
712 tok/s

427–1,139 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 4.8 GB Q8_0 Comfortable
712 tok/s

427–1,139 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 4.8 GB Q8_0 Comfortable
569 tok/s

342–911 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 4.8 GB Q8_0 Comfortable
545 tok/s

327–872 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 4.8 GB Q8_0 Comfortable
545 tok/s

327–872 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 4.8 GB Q8_0 Comfortable
522 tok/s

313–835 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 4.8 GB Q8_0 Comfortable
463 tok/s

278–741 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 4.8 GB Q8_0 Comfortable
463 tok/s

278–741 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 4.8 GB Q8_0 Comfortable
463 tok/s

278–741 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 4.8 GB Q8_0 Comfortable
439 tok/s

263–703 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 4.8 GB Q8_0 Comfortable
374 tok/s

225–599 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 4.8 GB Q8_0 Comfortable
374 tok/s

225–599 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 4.8 GB Q8_0 Comfortable
374 tok/s

225–599 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 4.8 GB Q8_0 Comfortable
374 tok/s

225–599 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 4.8 GB Q8_0 Comfortable
374 tok/s

225–599 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 4.8 GB Q8_0 Comfortable
285 tok/s

171–456 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 4.8 GB Q8_0 Comfortable
285 tok/s

171–456 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 4.8 GB Q8_0 Comfortable
238 tok/s

143–380 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 4.8 GB Q8_0 Comfortable
233 tok/s

140–372 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 4.8 GB Q8_0 Comfortable
227 tok/s

136–364 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 4.8 GB Q8_0 Comfortable
227 tok/s

136–364 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 4.8 GB Q8_0 Comfortable
227 tok/s

136–364 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 4.8 GB Q8_0 Comfortable
227 tok/s

136–364 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 4.8 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
Beijing Academy of Artificial Intelligence / BAAI
Organisation type
Academia
Country
China
Published
17 September 2024
Authors
Shitao Xiao, Yueze Wang, Junjie Zhou, Huaying Yuan, Xingrun Xing, Ruiran Yan, Shuting Wang, Tiejun Huang, Zheng Liu

What it does

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

Domain
Image generation
Task
Image 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
3.8B

Table 2

Training data
tokens

"The entire dataset comprises approximately 0.1 billion images." Stage Image Resolution Training Steps (K) Batch Size 1 256×256 500 1040 2 512×512 300 520 3 1024×1024 100 208 4 2240×2240 30 104 5 Multiple 80 104

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 A800 PCIe 40 GB
Chips used
104
Power draw
51.2 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
Open source

MIT License https://github.com/VectorSpaceLab/OmniGen

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
OmniGen: Unified Image Generation
Last updated
28 November 2025

The extremes

What the numbers mean

The hardware side

Minimum card

Tesla C1080

Memory needed

3.4 GB

Fastest

892 tok/s

OmniGen reaches a parameter count of 3.8B. 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.

At the low end it is handled by Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q5_K_M and producing around 17.3 tokens per second.

At the other end sits B200, generating roughly 892 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

What this model is

OmniGen was published by Beijing Academy of Artificial Intelligence / BAAI, in the country recorded as China, during September 2024. The publishing organisation is categorised as academia.

It works in the domain of Image generation, and is recorded as performing the task of image generation.

Published weights mean the model runs on your machine rather than someone else's, which is what makes the hardware question below answerable at all.

What decides the speed

The median result is around 29.9 tokens per second. Exceeding reading speed outright: 777 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.

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.

Step by step

How to choose a GPU for OmniGen

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

  1. 01

    Start from the memory column

    Start from what it actually needs, which is the requirement of OmniGen, needing around 3.4 GB at a compression of Q5_K_M. That figure, not the headline performance of a card, is what decides whether it runs.

  2. 02

    Match the context to your actual use

    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 OmniGen.

  3. 03

    Set a quality floor

    Each card runs the least-compressed copy it can hold, reaching a compression of Q5_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.

  4. 04

    Rank by throughput rather than spec sheet

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

  5. 05

    Check the fit verdict before buying

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

  6. 06

    Open the card you have settled on

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

Answers

OmniGen — common questions

01

OmniGen— how much VRAM does it need?

It needs about 3.4 GB at a compression of Q5_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.

02

OmniGen— 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.8 GB and generating roughly 166 tokens per second. The fit is comfortable.

03

OmniGen— 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.8 GB and generating roughly 102 tokens per second. The fit is comfortable.

04

OmniGen— 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.8 GB and generating roughly 126 tokens per second. The fit is comfortable.

05

OmniGen— 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.8 GB and generating roughly 149 tokens per second. The fit is comfortable.

06

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

07

OmniGen— how many parameters does it have?

It has a parameter count of 3.8B. Table 2. 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.

08

OmniGen— who created it?

It was published by Beijing Academy of Artificial Intelligence / BAAI, based in China, an organisation categorised as academia.

09

OmniGen— when was it released?

It was published in September 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

10

OmniGen— what is it used for?

It works in the domain of Image generation, and is recorded as handling the task of image 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.

11

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

12

OmniGen— can I run it 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 model is rarely worth using. Every figure here assumes the whole model is resident on the card.

13

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

14

OmniGen— why does the quantisation differ between cards?

Each card is shown running the least-compressed copy it can hold. The number of distinct compression levels across the cards that fit it: 3. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

15

OmniGen— how accurate are these speed estimates?

These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 535–1,427 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

16

OmniGen— 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 Q5_K_M using about 3.4 GB, and produces roughly 17.3 tokens per second. The number of cards able to run it in total: 818.

17

OmniGen— how fast is it on a GPU?

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

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.