Granite 3.0 2B TPS calculator

Open weights IBM 2.5B 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 · 14.8 tok/s

Fastest card

B200

1,355 tok/s · 180 GB

Which GPUs can run Granite 3.0 2B?

Set the inputs, read the answer

Context length tokens

A longer conversation needs more memory, which can push this model off smaller cards.

Minimum quality

Hides cards that would only fit the model by compressing it below this point.

Search cards

Card memory

Also show cards that cannot run it

818 cards match

Calculating

					Needs	Quantisation	Fit
1,355 tok/s 813–2,168 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	3.4 GB	Q8_0	Comfortable
1,355 tok/s 813–2,168 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	3.4 GB	Q8_0	Comfortable
1,082 tok/s 649–1,732 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	3.4 GB	Q8_0	Comfortable
1,082 tok/s 649–1,732 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	3.4 GB	Q8_0	Comfortable
866 tok/s 519–1,385 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	3.4 GB	Q8_0	Comfortable
828 tok/s 497–1,325 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	3.4 GB	Q8_0	Comfortable
828 tok/s 497–1,325 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	3.4 GB	Q8_0	Comfortable
793 tok/s 476–1,269 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	3.4 GB	Q8_0	Comfortable
704 tok/s 422–1,126 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	3.4 GB	Q8_0	Comfortable
704 tok/s 422–1,126 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	3.4 GB	Q8_0	Comfortable
704 tok/s 422–1,126 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	3.4 GB	Q8_0	Comfortable
667 tok/s 400–1,068 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	3.4 GB	Q8_0	Comfortable
569 tok/s 342–911 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	3.4 GB	Q8_0	Comfortable
569 tok/s 342–911 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	3.4 GB	Q8_0	Comfortable
569 tok/s 342–911 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	3.4 GB	Q8_0	Comfortable
569 tok/s 342–911 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	3.4 GB	Q8_0	Comfortable
569 tok/s 342–911 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	3.4 GB	Q8_0	Comfortable
433 tok/s 260–693 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	3.4 GB	Q8_0	Comfortable
433 tok/s 260–693 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	3.4 GB	Q8_0	Comfortable
361 tok/s 217–578 · low confidence	Data Center GPU Max 1550 Intel	128 GB	3,280 GB/s	Jan 2023	3.4 GB	Q8_0	Comfortable
353 tok/s 212–566 · low confidence	Data Center GPU Max Subsystem Intel	128 GB	3,210 GB/s	Jan 2023	3.4 GB	Q8_0	Comfortable
346 tok/s 207–553 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	3.4 GB	Q8_0	Comfortable
346 tok/s 207–553 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	3.4 GB	Q8_0	Comfortable
346 tok/s 207–553 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	3.4 GB	Q8_0	Comfortable
346 tok/s 207–553 · low confidence	H100 CNX NVIDIA	80 GB	2,040 GB/s	Mar 2023	3.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: IBM
Organisation type: Industry
Country: United States of America
Published: 21 October 2024
Authors: Granite Team IBM

What it does

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

Domain: Language
Task: Language modeling/generation, Question answering, Translation, Text summarization, Text classification, Code 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: 2.5B
Training data: 12,000,000,000,000 tokens

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: 1.8 × 10²³ FLOP
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 H100 SXM5 80GB
Chips used: 768
Chip-hours: 192,030
Power draw: 1.1 MW

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: Unreleased
Hugging Face: ibm-granite

How it is classified

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

Likely above 10²³ FLOP: Yes
Record confidence: Confident

Sources

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

Reference: Granite 3.0 Language Models
Last updated: 28 November 2025

The extremes

The ten fastest GPUs that run Granite 3.0 2B

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.

The smallest GPUs that still run Granite 3.0 2B

The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.

What the numbers mean

What you need to run it

Minimum card

Tesla C1080

Memory needed

3.4 GB

Fastest

1,355 tok/s

Granite 3.0 2B is small enough at 2.5B 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 14.8 tokens per second.

Top of the range is the B200, at roughly 1,355 tokens per second thanks to 8,000 GB/s of bandwidth.

About this model

Granite 3.0 2B was published by IBM, in United States of America, in October 2024. industry is the category the publisher falls under.

It works in Language, and is recorded as doing language modeling/generation, Question answering, Translation, Text summarization, Text classification, Code generation.

The weights being open is what puts this page in the calculator rather than only in the catalogue: it is a model you can actually hold. It is published under the ibm-granite organisation on Hugging Face.

How fast it runs, and why

The median result is around 38.1 tokens per second; 783 cards produce text faster than most people read it.

Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.

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.

How it was trained

The training run consumed about 1.8 × 10²³ FLOP, on NVIDIA H100 SXM5 80GB. That figure describes the cost of creating it and has no bearing on how quickly it generates text.

The training set ran to roughly 12,000,000,000,000 tokens.

Step by step

How to choose a GPU for Granite 3.0 2B

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

01

Check what it needs before anything else

The table lists every card that can hold Granite 3.0 2B — around 3.4 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
02

Match the context to your actual use

Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason Granite 3.0 2B stops fitting a card that seemed fine.
03

Choose how far you will compress it

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 Granite 3.0 2B by squeezing it further than you would want.
04

Sort by speed

Sort by speed to see how cards rank for Granite 3.0 2B. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 1,355 tok/s.
05

Check the fit verdict before buying

The fit column separates cards that just manage Granite 3.0 2B from those with room to spare. Buy for the second if the context might grow.
06

See what else that card runs

Following a card through to its own page shows every other model it can hold, which is the question that follows once Granite 3.0 2B is settled.

Answers

Granite 3.0 2B — common questions

Can I run Granite 3.0 2B on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 3.4 GB and generating roughly 227 tokens per second — a comfortable fit.

Is Granite 3.0 2B open source?

Its weights are published, so Granite 3.0 2B 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 Granite 3.0 2B have?

Granite 3.0 2B has 2.5B parameters. 2.5B. 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 Granite 3.0 2B?

Granite 3.0 2B was published by IBM, based in United States of America, categorised as industry.

When was Granite 3.0 2B released?

Granite 3.0 2B 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.

What is Granite 3.0 2B used for?

Granite 3.0 2B works in Language, and is recorded as handling language modeling/generation, Question answering, Translation, Text summarization, Text classification, Code generation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

Where can I download Granite 3.0 2B?

Its weights are published under the ibm-granite 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 Granite 3.0 2B?

Around 1.8 × 10²³ FLOP, on NVIDIA H100 SXM5 80GB. 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 Granite 3.0 2B 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 Granite 3.0 2B is rarely worth using. Every figure here assumes the whole model is on the card.

Would two GPUs run Granite 3.0 2B faster?

Two cards buy memory rather than speed. That matters for Granite 3.0 2B only if one card cannot hold it — 818 can, so a second adds little.

Why does the quantisation differ between cards for Granite 3.0 2B?

A larger card holds a more accurate copy. Across the cards that run Granite 3.0 2B, 1 compression levels are used; the floor control above pins it to one.

How accurate are these Granite 3.0 2B 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 813–2,168 tok/s on the B200 rather than a single number.

What GPU do I need to run Granite 3.0 2B?

The smallest card in our catalogue that holds Granite 3.0 2B is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 3.4 GB, and produces roughly 14.8 tokens per second. 818 cards in total can run it.

How fast is Granite 3.0 2B on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 1,355 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 783 of the cards that can run Granite 3.0 2B clear that.

How much VRAM does Granite 3.0 2B need?

About 3.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 Granite 3.0 2B on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 3.4 GB and generating roughly 252 tokens per second — a comfortable fit.

Can I run Granite 3.0 2B on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 3.4 GB and generating roughly 155 tokens per second — a comfortable fit.

Can I run Granite 3.0 2B on a 16 GB GPU?

Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 3.4 GB and generating roughly 191 tokens per second — a comfortable fit.

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.

All AI models