Janus-Pro-7B 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 K20c
5 GB · Q3_K_M · 28.9 tok/s
Fastest card
B200
484 tok/s · 180 GB
Which GPUs can run Janus-Pro-7B?
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.
589 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
484
tok/s
290–774 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 8.2 GB | Q8_0 | Comfortable |
|
484
tok/s
290–774 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 8.2 GB | Q8_0 | Comfortable |
|
387
tok/s
232–618 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 8.2 GB | Q8_0 | Comfortable |
|
387
tok/s
232–618 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 8.2 GB | Q8_0 | Comfortable |
|
309
tok/s
185–495 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 8.2 GB | Q8_0 | Comfortable |
|
296
tok/s
178–473 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 8.2 GB | Q8_0 | Comfortable |
|
296
tok/s
178–473 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 8.2 GB | Q8_0 | Comfortable |
|
283
tok/s
170–453 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 8.2 GB | Q8_0 | Comfortable |
|
251
tok/s
151–402 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 8.2 GB | Q8_0 | Comfortable |
|
251
tok/s
151–402 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 8.2 GB | Q8_0 | Comfortable |
|
251
tok/s
151–402 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 8.2 GB | Q8_0 | Comfortable |
|
238
tok/s
143–381 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 8.2 GB | Q8_0 | Comfortable |
|
155
tok/s
93–248 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 8.2 GB | Q8_0 | Comfortable |
|
155
tok/s
93–248 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 8.2 GB | Q8_0 | Comfortable |
|
131
tok/s
79–210 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 6.6 GB | Q6_K | Tight |
|
129
tok/s
77–206 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 8.2 GB | Q8_0 | Comfortable |
|
126
tok/s
76–202 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 8.2 GB | Q8_0 | Comfortable |
|
123
tok/s
74–197 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 8.2 GB | Q8_0 | Comfortable |
|
123
tok/s
74–197 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 8.2 GB | Q8_0 | Comfortable |
|
123
tok/s
74–197 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 8.2 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
- DeepSeek
- Organisation type
- Industry
- Country
- China
- Published
- 27 January 2025
- Authors
- Xiaokang Chen, Zhiyu Wu, Xingchao Liu, Zizheng Pan, Wen Liu, Zhenda Xie, Xingkai Yu, Chong Ruan
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Image generation, Vision, Language, Multimodal
- Task
- Image generation, Text-to-image, Visual question answering
- Base model
- DeepSeek LLM 7B,SigLIP 400M
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
- 7B
- Training data
- 3,138,560,000 tokens
- Epochs
- 1
7B In our experiments, we utilize DeepSeek-LLM (1.5B and 7B) [3] with a maximum supported sequence length of 4096 as the base language model. For the vision encoder used in understanding tasks, we select SigLIP-Large-Patch16-384 [53].
from table 2 assuming each sample is 384*384/(16*16) = 576 tokens (it might be less since it is not just image but text data as well but not OOM less) 20000*256 + 360000*512 + 40000*128) * 576 = 3138560000 tokens high confidence since it aligns well with the compute estimate
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,Operation counting
- Fine-tuning compute
- 9.1 × 10²⁰ FLOP
312000000000000 FLOP / GPU / sec * 336 hours * 3600 sec / hour * 8 GPUs * 0.3 [assumed utilization] = 9.05748×10^20 FLOP (it might be more if utilization is higher than 0.3) operation counting: from table 2 assuming each sample is 384*384/(16*16) = 576 tokens (it might be less since it is not just image but text data as well but not OOM less) 6 FLOP / parameter / token * ((20000*256 + 360000*512 + 40000*128) * 576) tokens * 7*10^9 parameters = 4.70679552 × 10^21 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 40 GB
- Chips used
- 8
- Wall-clock time
- 336 hours (14 days)
- Power draw
- 6.3 kW
"The whole training process took about 9/14 days on a cluster of 16/32 nodes for 1.5B/7B model, each equipped with 8 Nvidia A100 (40GB) GPUs." 14*24 = 336 hours
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 (restricted use)
- Hugging Face
- deepseek-ai
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
- Janus-Pro: Unified Multimodal Understanding and Generation with Data and Model Scaling
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Janus-Pro-7B
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 484 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 484 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 387 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 387 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 309 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 296 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 296 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 283 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 251 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 251 tok/s
The smallest GPUs that still run Janus-Pro-7B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Quadro P2200 5 GB · needs 4.1 GB · Q3_K_M · tight 27.8 tok/s
- 02 P102-100 5 GB · needs 4.1 GB · Q3_K_M · tight 61.1 tok/s
- 03 GeForce GTX 1060 5 GB 5 GB · needs 4.1 GB · Q3_K_M · tight 22.2 tok/s
- 04 Quadro P2000 5 GB · needs 4.1 GB · Q3_K_M · tight 19.5 tok/s
- 05 Tesla K20s 5 GB · needs 4.1 GB · Q3_K_M · tight 28.9 tok/s
- 06 Tesla K20m 5 GB · needs 4.1 GB · Q3_K_M · tight 28.9 tok/s
- 07 Tesla K20c 5 GB · needs 4.1 GB · Q3_K_M · tight 28.9 tok/s
- 08 RTX 1000 Mobile Ada Generation 6 GB · needs 4.9 GB · Q4_K_M · tight 26.8 tok/s
- 09 GeForce RTX 3050 6 GB 6 GB · needs 4.9 GB · Q4_K_M · tight 23.5 tok/s
- 10 Arc A380M 6 GB · needs 4.9 GB · Q4_K_M · tight 16.9 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla K20c
Memory needed
4.1 GB
Fastest
484 tok/s
Janus-Pro-7B is small enough at 7B parameters that hardware is rarely the obstacle — 589 of the cards we track can run it, including cards several years old.
The entry point is the Tesla K20c: 5 GB of memory, Q3_K_M compression, roughly 28.9 tokens per second.
A B200 is the fastest we calculate for it: about 484 tokens per second, from 8,000 GB/s of memory bandwidth.
What this model is
Janus-Pro-7B was published by DeepSeek, in China, in January 2025. The organisation is categorised as industry.
It works in Image generation, Vision, Language, Multimodal, and is recorded as doing image generation, Text-to-image, Visual question answering.
It is derived from DeepSeek LLM 7B,SigLIP 400M rather than trained from scratch, which is the usual way a specialised model is produced.
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. It is published under the deepseek-ai organisation on Hugging Face.
What decides the speed
The median result is around 26.1 tokens per second; 559 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.
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.
How it was trained
Around 3,138,560,000 tokens went into training it.
Step by step
How to choose a GPU for Janus-Pro-7B
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
Every card here has been checked against Janus-Pro-7B — around 4.1 GB at Q3_K_M. Capacity is the gate — a card either holds it or it does not.
-
02
Decide how long your conversations run
The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context Janus-Pro-7B can slip off a card that handles short questions easily.
-
03
Set a quality floor
Compression is what makes Janus-Pro-7B 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
Rank by throughput rather than spec sheet
The speed ordering for Janus-Pro-7B is effectively an ordering by memory bandwidth, which is why the B200 tops it at 484 tok/s.
-
05
Read the fit column last
A tight fit runs Janus-Pro-7B but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
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 Janus-Pro-7B.
Answers
Janus-Pro-7B — common questions
Is Janus-Pro-7B open source?
Its weights are published, so Janus-Pro-7B 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 Janus-Pro-7B have?
Janus-Pro-7B has 7B parameters. 7B In our experiments, we utilize DeepSeek-LLM (1.5B and 7B) [3] with a maximum supported sequence length of 4096 as the base language model. For the vision encoder used in understanding tasks, we select SigLIP-Large-Patch16-384 [53]. 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 Janus-Pro-7B?
Janus-Pro-7B was published by DeepSeek, based in China, categorised as industry.
When was Janus-Pro-7B released?
Janus-Pro-7B was published in January 2025.
What is Janus-Pro-7B used for?
Janus-Pro-7B works in Image generation, Vision, Language, Multimodal, and is recorded as handling image generation, Text-to-image, Visual question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download Janus-Pro-7B?
Its weights are published under the deepseek-ai organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
Can I run Janus-Pro-7B if it does not fit in my GPU?
It can be split between the card and system memory, but Janus-Pro-7B generates painfully slowly that way — the nearest miss we calculate is short by 1.3 GB. Nothing on this page assumes offloading.
Would two GPUs run Janus-Pro-7B faster?
Capacity adds across cards; throughput does not. Since 589 of the cards we track already hold Janus-Pro-7B on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for Janus-Pro-7B?
Each card is shown running the least-compressed copy it can hold, and Janus-Pro-7B appears at 4 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these Janus-Pro-7B speed estimates?
Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 290–774 tok/s on the B200 rather than a single number.
What GPU do I need to run Janus-Pro-7B?
The smallest card in our catalogue that holds Janus-Pro-7B is the Tesla K20c, with 5 GB of memory. It runs the model at Q3_K_M using about 4.1 GB, and produces roughly 28.9 tokens per second. 589 cards in total can run it.
How fast is Janus-Pro-7B on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 484 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 559 of the cards that can run Janus-Pro-7B clear that.
How much VRAM does Janus-Pro-7B need?
About 4.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 Janus-Pro-7B on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q6_K, using about 6.6 GB and generating roughly 131 tokens per second — a tight fit.
Can I run Janus-Pro-7B on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 8.2 GB and generating roughly 55.2 tokens per second — a comfortable fit.
Can I run Janus-Pro-7B on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 8.2 GB and generating roughly 68.4 tokens per second — a comfortable fit.
Can I run Janus-Pro-7B on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 8.2 GB and generating roughly 81.1 tokens per second — a comfortable fit.
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.