OmniGen 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 · 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
- Training data
- tokens
Table 2
"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
The ten fastest GPUs that run OmniGen
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 892 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 892 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 712 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 712 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 569 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 545 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 545 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 522 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 463 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 463 tok/s
The smallest GPUs that still run OmniGen
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 · Q5_K_M · tight 19.1 tok/s
- 02 RTX A400 4 GB · needs 3.4 GB · Q5_K_M · tight 19.1 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 3.4 GB · Q5_K_M · tight 25.5 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 3.4 GB · Q5_K_M · tight 38.2 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 3.4 GB · Q5_K_M · tight 6.8 tok/s
- 06 Radeon RX 6450M 4 GB · needs 3.4 GB · Q5_K_M · tight 19.9 tok/s
- 07 Radeon RX 6550M 4 GB · needs 3.4 GB · Q5_K_M · tight 22.4 tok/s
- 08 Radeon RX 6550S 4 GB · needs 3.4 GB · Q5_K_M · tight 19.9 tok/s
- 09 Arc A310 4 GB · needs 3.4 GB · Q5_K_M · tight 16.0 tok/s
- 10 Arc Pro A30M 4 GB · needs 3.4 GB · Q5_K_M · tight 16.6 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla C1080
Memory needed
3.4 GB
Fastest
892 tok/s
OmniGen is small enough at 3.8B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
At the low end, a Tesla C1080 handles it — 4 GB, at Q5_K_M, for about 17.3 tokens per second.
At the other end, a B200 generates roughly 892 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
What this model is
OmniGen was published by Beijing Academy of Artificial Intelligence / BAAI, in China, in September 2024. The organisation is categorised as academia.
It works in Image generation, and is recorded as doing 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; 777 cards produce text faster than most people read it.
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.
-
01
Start from the memory column
Look at what OmniGen actually needs — around 3.4 GB at Q5_K_M. No amount of processing power compensates for a card that cannot hold it.
-
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 OmniGen stops fitting a card that seemed fine.
-
03
Set a quality floor
Each card runs the least-compressed copy it can hold — Q5_K_M on the smallest card that fits. Setting a floor drops the cards that only manage OmniGen by squeezing it further than you would want.
-
04
Rank by throughput rather than spec sheet
Ranking by tokens per second for OmniGen follows memory bandwidth, not core counts, which is why the B200 tops it at 892 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs OmniGen but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
06
Open the card you have settled on
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond OmniGen.
Answers
OmniGen — common questions
How much VRAM does OmniGen need?
About 3.4 GB at Q5_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 OmniGen on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 4.8 GB and generating roughly 166 tokens per second — a comfortable fit.
Can I run OmniGen on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 4.8 GB and generating roughly 102 tokens per second — a comfortable fit.
Can I run OmniGen on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 4.8 GB and generating roughly 126 tokens per second — a comfortable fit.
Can I run OmniGen on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 4.8 GB and generating roughly 149 tokens per second — a comfortable fit.
Is OmniGen open source?
Its weights are published, so OmniGen 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 OmniGen have?
OmniGen has 3.8B parameters. 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.
Who created OmniGen?
OmniGen was published by Beijing Academy of Artificial Intelligence / BAAI, based in China, categorised as academia.
When was OmniGen released?
OmniGen 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.
What is OmniGen used for?
OmniGen works in Image generation, and is recorded as handling 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.
Where can I download OmniGen?
The weights for OmniGen are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Can I run OmniGen 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 OmniGen is rarely worth using. Every figure here assumes the whole model is on the card.
Would two GPUs run OmniGen faster?
Two cards buy memory rather than speed. That matters for OmniGen only if one card cannot hold it — 818 can, so a second adds little.
Why does the quantisation differ between cards for OmniGen?
Each card is shown running the least-compressed copy it can hold, and OmniGen appears at 3 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these OmniGen speed estimates?
These are estimates with real error bars. The fastest result here, 535–1,427 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.
What GPU do I need to run OmniGen?
The smallest card in our catalogue that holds OmniGen is the Tesla C1080, with 4 GB of memory. It runs the model at Q5_K_M using about 3.4 GB, and produces roughly 17.3 tokens per second. 818 cards in total can run it.
How fast is OmniGen on a GPU?
It depends on the card. The quickest we calculate is a 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 777 of the cards that can run OmniGen clear that.
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.