BLOOM-560M 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 · 65.8 tok/s
Fastest card
B200
6,050 tok/s · 180 GB
Which GPUs can run BLOOM-560M?
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 | |||||
|---|---|---|---|---|---|---|---|
|
6,050
tok/s
3,630–9,681 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.3 GB | Q8_0 | Comfortable |
|
6,050
tok/s
3,630–9,681 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.3 GB | Q8_0 | Comfortable |
|
4,831
tok/s
2,899–7,730 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.3 GB | Q8_0 | Comfortable |
|
4,831
tok/s
2,899–7,730 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.3 GB | Q8_0 | Comfortable |
|
3,864
tok/s
2,318–6,182 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.3 GB | Q8_0 | Comfortable |
|
3,698
tok/s
2,219–5,917 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.3 GB | Q8_0 | Comfortable |
|
3,698
tok/s
2,219–5,917 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.3 GB | Q8_0 | Comfortable |
|
3,540
tok/s
2,124–5,663 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.3 GB | Q8_0 | Comfortable |
|
3,141
tok/s
1,885–5,026 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.3 GB | Q8_0 | Comfortable |
|
3,141
tok/s
1,885–5,026 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.3 GB | Q8_0 | Comfortable |
|
3,141
tok/s
1,885–5,026 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,980
tok/s
1,788–4,768 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.3 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,541
tok/s
1,525–4,066 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
1,935
tok/s
1,161–3,096 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.3 GB | Q8_0 | Comfortable |
|
1,935
tok/s
1,161–3,096 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.3 GB | Q8_0 | Comfortable |
|
1,612
tok/s
967–2,580 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.3 GB | Q8_0 | Comfortable |
|
1,578
tok/s
947–2,525 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.3 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.3 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.3 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.3 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.3 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
- Hugging Face,BigScience
- Organisation type
- Industry,Research collective
- Country
- United States of America, France
- Published
- 5 July 2022
- Authors
- Margaret Mitchell, Giada Pistilli, Yacine Jernite, Ezinwanne Ozoani, Marissa Gerchick, Nazneen Rajani, Sasha Luccioni, Irene Solaiman, Maraim Masoud, Somaieh Nikpoor, Carlos Muñoz Ferrandis, Stas Bekman, Christopher Akiki, Danish Contractor, David Lansky, Angelina McMillan-Major, Tristan Thrush, Suzana Ilić, Gérard Dupont, Shayne Longpre, Manan Dey, Stella Biderman, Douwe Kiela, Emi Baylor, Teven …
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/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
- 560M
- Training data
- 354,000,000,000 tokens
- Epochs
- 1
Table 3.5 https://arxiv.org/pdf/2211.05100 341B (pretrain) + 13B (finetune) = 354B tokens total
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
- Unreleased
commercial, no harmful use: https://bigscience.huggingface.co/blog/the-bigscience-rail-license
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
- Citations
- 2,917
- Benchmark data
- BLOOM-560M
Sources
Where this record came from and when it was last checked.
- Reference
- BigScience Language Open-science Open-access Multilingual (BLOOM) Language Model
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run BLOOM-560M
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 6,050 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 6,050 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 4,831 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 4,831 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 3,864 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 3,698 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 3,698 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 3,540 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 3,141 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 3,141 tok/s
The smallest GPUs that still run BLOOM-560M
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 1.3 GB · Q8_0 · comfortable 72.6 tok/s
- 02 RTX A400 4 GB · needs 1.3 GB · Q8_0 · comfortable 72.6 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.3 GB · Q8_0 · comfortable 96.8 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.3 GB · Q8_0 · comfortable 145 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.3 GB · Q8_0 · comfortable 25.8 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.3 GB · Q8_0 · comfortable 75.5 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.3 GB · Q8_0 · comfortable 85.0 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.3 GB · Q8_0 · comfortable 75.5 tok/s
- 09 Arc A310 4 GB · needs 1.3 GB · Q8_0 · comfortable 61.0 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.3 GB · Q8_0 · comfortable 62.9 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
1.3 GB
Fastest
6,050 tok/s
BLOOM-560M is small enough at 560M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The least hardware that works is a Tesla C1080. Its 4 GB is enough at Q8_0 compression, giving roughly 65.8 tokens per second.
A B200 is the fastest we calculate for it: about 6,050 tokens per second, from 8,000 GB/s of memory bandwidth.
What this model is
BLOOM-560M was published by Hugging Face,BigScience, in United States of America, in July 2022. It comes out of industry,Research collective.
It works in Language, and is recorded as doing language modeling/generation.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.
What decides the speed
Half the cards that hold it manage more than 169.9 tokens per second, and 809 exceed reading speed outright.
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.
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.
Training and provenance
It was trained on about 354,000,000,000 tokens of text.
Step by step
How to choose a GPU for BLOOM-560M
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 BLOOM-560M actually needs — around 1.3 GB at Q8_0. No amount of processing power compensates for a card that cannot hold it.
-
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 BLOOM-560M can slip off a card that handles short questions easily.
-
03
Set a quality floor
The quantisation column varies by card, because a bigger card holds a more accurate copy of BLOOM-560M — Q8_0 on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Sort by speed
Sort by speed to see how cards rank for BLOOM-560M. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 6,050 tok/s.
-
05
Read the fit column last
The fit column separates cards that just manage BLOOM-560M from those with room to spare. Buy for the second if the context might grow.
-
06
See what else that card runs
Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for BLOOM-560M alone — a card is usually bought for more than one model.
Answers
BLOOM-560M — common questions
How much VRAM does BLOOM-560M need?
About 1.3 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 BLOOM-560M on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.3 GB and generating roughly 1,127 tokens per second — a comfortable fit.
Can I run BLOOM-560M on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.3 GB and generating roughly 690 tokens per second — a comfortable fit.
Can I run BLOOM-560M on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.3 GB and generating roughly 855 tokens per second — a comfortable fit.
Can I run BLOOM-560M on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.3 GB and generating roughly 1,013 tokens per second — a comfortable fit.
Is BLOOM-560M open source?
Its weights are published, so BLOOM-560M 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 BLOOM-560M have?
BLOOM-560M has 560M parameters. 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 BLOOM-560M?
BLOOM-560M was published by Hugging Face,BigScience, based in United States of America, categorised as industry,Research collective.
When was BLOOM-560M released?
BLOOM-560M was published in July 2022. 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 BLOOM-560M used for?
BLOOM-560M works in Language, and is recorded as handling language modeling/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 BLOOM-560M?
The weights for BLOOM-560M 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 BLOOM-560M if it does not fit in my GPU?
It can be split between the card and system memory, but BLOOM-560M generates painfully slowly that way. Nothing on this page assumes offloading.
Would two GPUs run BLOOM-560M faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run BLOOM-560M alone, the case for pairing is weak.
Why does the quantisation differ between cards for BLOOM-560M?
Because capacity varies, so does how hard BLOOM-560M has to be squeezed — 1 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these BLOOM-560M speed estimates?
These are estimates with real error bars. The fastest result here, 3,630–9,681 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 BLOOM-560M?
The smallest card in our catalogue that holds BLOOM-560M is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.3 GB, and produces roughly 65.8 tokens per second. 818 cards in total can run it.
How fast is BLOOM-560M on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 6,050 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 809 of the cards that can run BLOOM-560M 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.