Kosmos-2 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 · 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
- Training data
- 25,000,000,000 tokens
1.6B
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
- How it was established
- Operation counting,Hardware
"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.
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
- Power draw
- 152.8 kW
" We train the model on 256 V100 GPUs and the training takes approximately one day to complete"
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
- Hugging Face
- microsoft
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
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
The ten fastest GPUs that run Kosmos-2
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 2,118 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 2,118 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 1,691 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 1,691 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 1,352 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 1,294 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 1,294 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 1,239 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 1,099 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 1,099 tok/s
The smallest GPUs that still run Kosmos-2
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 2.4 GB · Q8_0 · comfortable 25.4 tok/s
- 02 RTX A400 4 GB · needs 2.4 GB · Q8_0 · comfortable 25.4 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 2.4 GB · Q8_0 · comfortable 33.9 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 2.4 GB · Q8_0 · comfortable 50.8 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 2.4 GB · Q8_0 · comfortable 9.0 tok/s
- 06 Radeon RX 6450M 4 GB · needs 2.4 GB · Q8_0 · comfortable 26.4 tok/s
- 07 Radeon RX 6550M 4 GB · needs 2.4 GB · Q8_0 · comfortable 29.7 tok/s
- 08 Radeon RX 6550S 4 GB · needs 2.4 GB · Q8_0 · comfortable 26.4 tok/s
- 09 Arc A310 4 GB · needs 2.4 GB · Q8_0 · comfortable 21.3 tok/s
- 10 Arc Pro A30M 4 GB · needs 2.4 GB · Q8_0 · comfortable 22.0 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
2.4 GB
Fastest
2,118 tok/s
Kosmos-2 is small enough at 1.6B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The entry point is the Tesla C1080: 4 GB of memory, Q8_0 compression, roughly 23.0 tokens per second.
At the other end, a B200 generates roughly 2,118 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.
Background
Kosmos-2 was published by Microsoft, in United States of America, in June 2023. industry is the category the publisher falls under.
It works in Language, Vision, Multimodal, and is recorded as doing 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. It is published under the microsoft organisation on Hugging Face.
Reading the throughput figures
Across every card that can run it, the middle of the range is about 59.5 tokens per second, and 794 of them clear the ten tokens per second that roughly matches reading speed.
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 NVIDIA V100. That figure describes the cost of creating it and has no bearing on how quickly it generates text.
Around 25,000,000,000 tokens went into training it.
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.
-
01
Read the memory figure first
Every card here has been checked against Kosmos-2 — around 2.4 GB at Q8_0. Capacity is the gate — a card either holds it or it does not.
-
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.
-
03
Set a quality floor
Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage Kosmos-2 by squeezing it further than you would want.
-
04
Compare tokens per second, not specifications
The speed ordering for Kosmos-2 is effectively an ordering by memory bandwidth, which is why the B200 tops it at 2,118 tok/s.
-
05
Look at the headroom, not just the fit
A tight fit runs Kosmos-2 but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
06
See what else that card runs
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond Kosmos-2.
Answers
Kosmos-2 — common questions
Where can I download Kosmos-2?
Its weights are published under the microsoft organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train Kosmos-2?
Around 4.6 × 10²⁰ FLOP, on 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.
Can I run Kosmos-2 if it does not fit in my GPU?
It can be split between the card and system memory, but Kosmos-2 generates painfully slowly that way. Nothing on this page assumes offloading.
Would two GPUs run Kosmos-2 faster?
Capacity adds across cards; throughput does not. Since 818 of the cards we track already hold Kosmos-2 on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for Kosmos-2?
Because capacity varies, so does how hard Kosmos-2 has to be squeezed — 1 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these Kosmos-2 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 1,271–3,388 tok/s on the B200 rather than a single number.
What GPU do I need to run Kosmos-2?
The smallest card in our catalogue that holds Kosmos-2 is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 2.4 GB, and produces roughly 23.0 tokens per second. 818 cards in total can run it.
How fast is Kosmos-2 on a GPU?
It depends on the card. The quickest we calculate is a 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 794 of the cards that can run Kosmos-2 clear that.
How much VRAM does Kosmos-2 need?
About 2.4 GB at Q8_0 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 Kosmos-2 on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 2.4 GB and generating roughly 394 tokens per second — a comfortable fit.
Can I run Kosmos-2 on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 2.4 GB and generating roughly 242 tokens per second — a comfortable fit.
Can I run Kosmos-2 on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 2.4 GB and generating roughly 299 tokens per second — a comfortable fit.
Can I run Kosmos-2 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 2.4 GB and generating roughly 355 tokens per second — a comfortable fit.
Is Kosmos-2 open source?
Its weights are published, so Kosmos-2 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 Kosmos-2 have?
Kosmos-2 has 1.6B parameters. 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.
Who created Kosmos-2?
Kosmos-2 was published by Microsoft, based in United States of America, categorised as industry.
When was Kosmos-2 released?
Kosmos-2 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.
What is Kosmos-2 used for?
Kosmos-2 works in Language, Vision, Multimodal, and is recorded as handling 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.
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.