Janus 1.3B TPS calculator

Open weights DeepSeek,The University of Hong Kong,Peking University 1.3B parameters October 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 · Q8_0 · 28.4 tok/s

Fastest card

B200

2,606 tok/s · 180 GB

Which GPUs can run Janus 1.3B?

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
2,606 tok/s

1,564–4,170 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 2.1 GB Q8_0 Comfortable
2,606 tok/s

1,564–4,170 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 2.1 GB Q8_0 Comfortable
2,081 tok/s

1,249–3,330 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 2.1 GB Q8_0 Comfortable
2,081 tok/s

1,249–3,330 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 2.1 GB Q8_0 Comfortable
1,664 tok/s

999–2,663 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 2.1 GB Q8_0 Comfortable
1,593 tok/s

956–2,549 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 2.1 GB Q8_0 Comfortable
1,593 tok/s

956–2,549 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 2.1 GB Q8_0 Comfortable
1,525 tok/s

915–2,440 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 2.1 GB Q8_0 Comfortable
1,353 tok/s

812–2,165 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 2.1 GB Q8_0 Comfortable
1,353 tok/s

812–2,165 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 2.1 GB Q8_0 Comfortable
1,353 tok/s

812–2,165 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 2.1 GB Q8_0 Comfortable
1,284 tok/s

770–2,054 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 2.1 GB Q8_0 Comfortable
1,095 tok/s

657–1,751 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.1 GB Q8_0 Comfortable
1,095 tok/s

657–1,751 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 2.1 GB Q8_0 Comfortable
1,095 tok/s

657–1,751 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 2.1 GB Q8_0 Comfortable
1,095 tok/s

657–1,751 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.1 GB Q8_0 Comfortable
1,095 tok/s

657–1,751 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 2.1 GB Q8_0 Comfortable
834 tok/s

500–1,334 · low confidence

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

500–1,334 · low confidence

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

417–1,111 · low confidence

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

408–1,088 · low confidence

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

399–1,063 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 2.1 GB Q8_0 Comfortable
665 tok/s

399–1,063 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 2.1 GB Q8_0 Comfortable
665 tok/s

399–1,063 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 2.1 GB Q8_0 Comfortable
665 tok/s

399–1,063 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 2.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
DeepSeek,The University of Hong Kong,Peking University
Organisation type
Industry,Academia,Academia
Country
China, Hong Kong
Published
17 October 2024
Authors
Chengyue Wu, Xiaokang Chen, Zhiyu Wu, Yiyang Ma, Xingchao Liu, Zizheng Pan, Wen Liu, Zhenda Xie, Xingkai Yu, Chong Ruan, Ping Luo

What it does

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

Domain
Language, Vision, Multimodal
Task
Language modeling/generation, Question answering, Visual question answering
Base model
DeepSeek-LLM-1.3b-base

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
1.3B

1.3B ! In the paper they say that they "utilize DeepSeek-LLM (1.3B) [5] with a maximum supported sequence length of 4096 as the base language model." but I haven't found any mentioning of 1.3B model in that Deepseek paper (only 7B and 67B)

Training data
tokens

"All images are resized to 384 × 384 pixels." Stage 1 Training steps 10, 000 Batch size 256 Stage 2 Training steps 180, 000 Batch size 512 Stage 3 Training steps 24, 000 Batch size 256 Since they are using SigLIP-Large-Patch16-384, patching size of 16*16 "For image generation, Janus uses the tokenizer from here with a downsample rate of 16." It is not enough information about text tokens and split between text and image tokens to calculate the total count

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
9.1 × 10²⁰ FLOP

311840000000000 FLOP / GPU / sec * 16 GPUs * 168 hours * 3600 sec / hour * 0.3 [assumed utilization] = 9.05284×10^20 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
16
Wall-clock time
168 hours (7 days)

"The whole training process took 7 days on a cluster of 16 nodes, each equipped with 8 Nvidia A100 (40GB) GPUs."

Power draw
12.6 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 (restricted use)
Training code
Open source

MIT License for code https://github.com/deepseek-ai/Janus https://huggingface.co/deepseek-ai/Janus-1.3B Deepseek License for weights https://github.com/deepseek-ai/DeepSeek-LLM/blob/HEAD/LICENSE-MODEL

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: Decoupling Visual Encoding for Unified Multimodal Understanding and Generation
Last updated
28 November 2025

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

Tesla C1080

Memory needed

2.1 GB

Fastest

2,606 tok/s

Janus 1.3B reaches a parameter count of 1.3B. 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 Q8_0 and producing around 28.4 tokens per second.

The fastest we calculate for it is B200, generating roughly 2,606 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

Where it came from

Janus 1.3B was published by DeepSeek,The University of Hong Kong,Peking University, in the country recorded as China, during October 2024. The publishing organisation is categorised as industry,Academia,Academia.

It works in the domain of Language, Vision, Multimodal, and is recorded as performing the task of language modeling/generation, Question answering, Visual question answering.

Its starting point was an existing base model, DeepSeek-LLM-1.3b-base. Most models at this scale are adapted from an existing base rather than built from nothing.

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. On Hugging Face it is published under the organisation deepseek-ai.

Understanding the speeds

The median result is around 73.2 tokens per second. Exceeding reading speed outright: 797 of them.

It is a dense model, so every parameter is read for every token produced. That makes speed track memory bandwidth almost exactly — a card with twice the bandwidth generates roughly twice as fast.

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.

Step by step

How to choose a GPU for Janus 1.3B

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

    Every card here has been checked against Janus 1.3B, needing around 2.1 GB at a compression of Q8_0. Capacity is the gate — a card either holds it or it does not.

  2. 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, because at long context a card that handles short questions easily can be dropped by Janus 1.3B.

  3. 03

    Decide how much compression you will accept

    Compression is what makes a model fit smaller cards, at some cost in accuracy, reaching a compression of Q8_0 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

    Sort by speed

    The speed ordering is effectively an ordering by memory bandwidth, for Janus 1.3B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 2,606 tok/s.

  5. 05

    Read the fit column last

    The fit column separates cards that just manage it from those with room to spare, in the case of Janus 1.3B. 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

    Check the card from the other side

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

Answers

Janus 1.3B — common questions

01

Janus 1.3B— 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.

02

Janus 1.3B— why does the quantisation differ between cards?

A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

03

Janus 1.3B— 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: 1,564–4,170 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

04

Janus 1.3B— 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 Q8_0 using about 2.1 GB, and produces roughly 28.4 tokens per second. The number of cards able to run it in total: 818.

05

Janus 1.3B— how fast is it on a GPU?

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

06

Janus 1.3B— how much VRAM does it need?

It needs about 2.1 GB at a compression of Q8_0, 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.

07

Janus 1.3B— 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 2.1 GB and generating roughly 485 tokens per second. The fit is comfortable.

08

Janus 1.3B— 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 2.1 GB and generating roughly 297 tokens per second. The fit is comfortable.

09

Janus 1.3B— 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 2.1 GB and generating roughly 368 tokens per second. The fit is comfortable.

10

Janus 1.3B— 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 2.1 GB and generating roughly 437 tokens per second. The fit is comfortable.

11

Janus 1.3B— 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.

12

Janus 1.3B— how many parameters does it have?

It has a parameter count of 1.3B. 1.3B ! In the paper they say that they "utilize DeepSeek-LLM (1.3B) [5] with a maximum supported sequence length of 4096 as the base language model." but I haven't found any mentioning of 1.3B model in that Deepseek paper (only 7B and 67B). 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.

13

Janus 1.3B— who created it?

It was published by DeepSeek,The University of Hong Kong,Peking University, based in China, an organisation categorised as industry,Academia,Academia.

14

Janus 1.3B— when was it released?

It was published in October 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.

15

Janus 1.3B— what is it used for?

It works in the domain of Language, Vision, Multimodal, and is recorded as handling the task of language modeling/generation, Question answering, Visual question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

16

Janus 1.3B— where can I download it?

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

17

Janus 1.3B— 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.

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.