Kosmos-2 TPS calculator

Open weights Microsoft 1.6B parameters June 2023

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 · 23.0 tok/s

Fastest card

B200

2,118 tok/s · 180 GB

Which GPUs can run Kosmos-2?

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

1,271–3,388 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 2.4 GB Q8_0 Comfortable
2,118 tok/s

1,271–3,388 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 2.4 GB Q8_0 Comfortable
1,691 tok/s

1,015–2,706 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 2.4 GB Q8_0 Comfortable
1,691 tok/s

1,015–2,706 · low confidence

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

811–2,164 · low confidence

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

777–2,071 · low confidence

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

777–2,071 · low confidence

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

743–1,982 · low confidence

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

660–1,759 · low confidence

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

660–1,759 · low confidence

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

660–1,759 · low confidence

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

626–1,669 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 2.4 GB Q8_0 Comfortable
889 tok/s

534–1,423 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.4 GB Q8_0 Comfortable
889 tok/s

534–1,423 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 2.4 GB Q8_0 Comfortable
889 tok/s

534–1,423 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 2.4 GB Q8_0 Comfortable
889 tok/s

534–1,423 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 2.4 GB Q8_0 Comfortable
889 tok/s

534–1,423 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 2.4 GB Q8_0 Comfortable
677 tok/s

406–1,084 · low confidence

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

406–1,084 · low confidence

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

339–903 · low confidence

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

331–884 · low confidence

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

324–864 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 2.4 GB Q8_0 Comfortable
540 tok/s

324–864 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 2.4 GB Q8_0 Comfortable
540 tok/s

324–864 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 2.4 GB Q8_0 Comfortable
540 tok/s

324–864 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 2.4 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
Microsoft
Organisation type
Industry
Country
United States of America
Published
26 June 2023
Authors
Zhiliang Peng, Wenhui Wang, Li Dong, Yaru Hao, Shaohan Huang, Shuming Ma, Furu Wei

What it does

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

Domain
Language, Vision, Multimodal
Task
Visual question answering, Image captioning, Named entity recognition (NER), Character recognition (OCR), Document representation
Approach
Self-supervised learning

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.6B

1.6B

Training data
25,000,000,000 tokens

text and images "We train KOSMOS-2 for 60k steps, equivalent to around 25 billion tokens" "We train the model on newly added grounded image-text pairs, monomodal text corpora, image-caption pairs, and interleaved image-text data. Our training process involves a batch size of 419K tokens, consisting of 185K tokens from text corpora, 215K tokens from original and grounded image-caption pairs, and 19K tokens from interleaved data. We train KOSMOS-2 for 60k steps, equivalent to around 25 billion to…

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

"We train the model on 256 V100 GPUs and the training takes approximately one day to complete" "We train KOSMOS-2 for 60k steps, equivalent to around 25 billion tokens" GPU-time method (256) * (1.3e14) * (24 * 3600) * (0.3) = 8.626176e20 (num gpu) * (peak flops) * (time in seconds) * (assumed utilization rate) Parameter-data method 6ND = 6*25B*1.6B = 2.4e20 Used geometric mean of two estimates.

How it was established
Operation counting,Hardware

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 V100
Chips used
256
Chip-hours
6,144
Wall-clock time
24 hours

" We train the model on 256 V100 GPUs and the training takes approximately one day to complete"

Power draw
152.8 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

data: https://huggingface.co/datasets/zzliang/GRIT weights and code, includes training: https://github.com/microsoft/unilm/tree/master/kosmos-2 license for full repo (MIT): https://github.com/microsoft/unilm/blob/master/LICENSE MIT license https://huggingface.co/microsoft/kosmos-2-patch14-224

Hugging Face
microsoft

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Record confidence
Likely
Citations
1,180

Sources

Where this record came from and when it was last checked.

Reference
Kosmos-2: Grounding Multimodal Large Language Models to the World
Last updated
25 May 2026

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

Tesla C1080

Memory needed

2.4 GB

Fastest

2,118 tok/s

Kosmos-2 reaches a parameter count of 1.6B. 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 23.0 tokens per second.

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

Background

Kosmos-2 was published by Microsoft, in the country recorded as United States of America, during June 2023. The category the publisher falls under is industry.

It works in the domain of Language, Vision, Multimodal, and is recorded as performing the task of visual question answering, Image captioning, Named entity recognition (NER), Character recognition (OCR), Document representation.

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. On Hugging Face it is published under the organisation microsoft.

Reading the throughput figures

Across every card that can run it, the middle of the range sits at 59.5 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 794 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.

How it was trained

The training run consumed about 4.6 × 10²⁰ FLOP, on hardware recorded as NVIDIA V100. That figure measures what producing the model cost, and has no bearing on how fast it answers.

Training consumed a corpus of around 25,000,000,000 tokens of text.

Step by step

How to choose a GPU for Kosmos-2

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

  1. 01

    Read the memory figure first

    Every card here has been checked against Kosmos-2, needing around 2.4 GB at a compression of Q8_0. No amount of processing power compensates for a card that cannot hold it.

  2. 02

    Decide how long your conversations run

    Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Kosmos-2.

  3. 03

    Set a quality floor

    Each card runs the least-compressed copy it can hold, 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

    Compare tokens per second, not specifications

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

  5. 05

    Look at the headroom, not just the fit

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

    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 Kosmos-2.

Answers

Kosmos-2 — common questions

01

Kosmos-2— where can I download it?

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

02

Kosmos-2— how much compute was used to train it?

Training consumed around 4.6 × 10²⁰ FLOP, on hardware recorded as NVIDIA V100. 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.

03

Kosmos-2— can I run it if it does not fit in my GPU?

It can be split between the card and system memory, but it generates painfully slowly that way. Every figure here assumes the whole model is resident on the card.

04

Kosmos-2— 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.

05

Kosmos-2— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

06

Kosmos-2— how accurate are these speed estimates?

Every figure is derived from memory bandwidth and model size, not benchmarked, which is why each is published as a range rather than a single number. One example: 1,271–3,388 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

07

Kosmos-2— 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.4 GB, and produces roughly 23.0 tokens per second. The number of cards able to run it in total: 818.

08

Kosmos-2— how fast is it on a GPU?

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

09

Kosmos-2— how much VRAM does it need?

It needs about 2.4 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.

10

Kosmos-2— 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.4 GB and generating roughly 394 tokens per second. The fit is comfortable.

11

Kosmos-2— 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.4 GB and generating roughly 242 tokens per second. The fit is comfortable.

12

Kosmos-2— 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.4 GB and generating roughly 299 tokens per second. The fit is comfortable.

13

Kosmos-2— 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.4 GB and generating roughly 355 tokens per second. The fit is comfortable.

14

Kosmos-2— 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.

15

Kosmos-2— how many parameters does it have?

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

16

Kosmos-2— who created it?

It was published by Microsoft, based in United States of America, an organisation categorised as industry.

17

Kosmos-2— when was it released?

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

18

Kosmos-2— what is it used for?

It works in the domain of Language, Vision, Multimodal, and is recorded as handling the task of visual question answering, Image captioning, Named entity recognition (NER), Character recognition (OCR), Document representation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

Source

Original publication

Record last updated 25 May 2026

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.