Granite 4.1 3B TPS calculator

Open weights IBM 3B parameters April 2026

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

Fastest card

B200

1,129 tok/s · 180 GB

Which GPUs can run Granite 4.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
1,129 tok/s

678–1,807 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 3.9 GB Q8_0 Comfortable
1,129 tok/s

678–1,807 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 3.9 GB Q8_0 Comfortable
902 tok/s

541–1,443 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 3.9 GB Q8_0 Comfortable
902 tok/s

541–1,443 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 3.9 GB Q8_0 Comfortable
721 tok/s

433–1,154 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 3.9 GB Q8_0 Comfortable
690 tok/s

414–1,105 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 3.9 GB Q8_0 Comfortable
690 tok/s

414–1,105 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 3.9 GB Q8_0 Comfortable
661 tok/s

396–1,057 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 3.9 GB Q8_0 Comfortable
586 tok/s

352–938 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 3.9 GB Q8_0 Comfortable
586 tok/s

352–938 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 3.9 GB Q8_0 Comfortable
586 tok/s

352–938 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 3.9 GB Q8_0 Comfortable
556 tok/s

334–890 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 3.9 GB Q8_0 Comfortable
474 tok/s

285–759 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 3.9 GB Q8_0 Comfortable
474 tok/s

285–759 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 3.9 GB Q8_0 Comfortable
474 tok/s

285–759 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 3.9 GB Q8_0 Comfortable
474 tok/s

285–759 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 3.9 GB Q8_0 Comfortable
474 tok/s

285–759 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 3.9 GB Q8_0 Comfortable
361 tok/s

217–578 · low confidence

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

217–578 · low confidence

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

181–482 · low confidence

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

177–471 · low confidence

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

173–461 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 3.9 GB Q8_0 Comfortable
288 tok/s

173–461 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 3.9 GB Q8_0 Comfortable
288 tok/s

173–461 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 3.9 GB Q8_0 Comfortable
288 tok/s

173–461 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 3.9 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
30 April 2026

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
3B
Training data
tokens

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)

The extremes

What the numbers mean

The hardware side

Minimum card

Tesla C1080

Memory needed

3.2 GB

Fastest

1,129 tok/s

Granite 4.1 3B reaches a parameter count of 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.

At the low end it is handled by Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q6_K and producing around 17.9 tokens per second.

The quickest result comes from B200, generating roughly 1,129 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

Where it came from

Granite 4.1 3B was published by IBM, in the country recorded as United States of America, during April 2026. The publishing organisation is categorised as industry.

It works in the domain of Language, and is recorded as performing the task of language modeling/generation.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.

Understanding the speeds

Across every card that can run it, the middle of the range sits at 35.8 tokens per second. Producing text faster than most people read it: 780 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 Granite 4.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

    Start from the memory column

    The table lists every card able to hold Granite 4.1 3B, needing around 3.2 GB at a compression of Q6_K. Capacity is the gate — a card either holds it or it does not.

  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 Granite 4.1 3B.

  3. 03

    Set a quality floor

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

    Ranking by tokens per second follows memory bandwidth rather than core counts, for Granite 4.1 3B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 1,129 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 Granite 4.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

    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 you have settled on Granite 4.1 3B.

Answers

Granite 4.1 3B — common questions

01

Granite 4.1 3B— where can I download it?

The weights are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

02

Granite 4.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.

03

Granite 4.1 3B— 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.

04

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

05

Granite 4.1 3B— 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: 678–1,807 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

06

Granite 4.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 Q6_K using about 3.2 GB, and produces roughly 17.9 tokens per second. The number of cards able to run it in total: 818.

07

Granite 4.1 3B— how fast is it on a GPU?

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

08

Granite 4.1 3B— how much VRAM does it need?

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

09

Granite 4.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 3.9 GB and generating roughly 210 tokens per second. The fit is comfortable.

10

Granite 4.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 3.9 GB and generating roughly 129 tokens per second. The fit is comfortable.

11

Granite 4.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 3.9 GB and generating roughly 160 tokens per second. The fit is comfortable.

12

Granite 4.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 3.9 GB and generating roughly 189 tokens per second. The fit is comfortable.

13

Granite 4.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.

14

Granite 4.1 3B— how many parameters does it have?

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

15

Granite 4.1 3B— who created it?

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

16

Granite 4.1 3B— when was it released?

It was published in April 2026.

17

Granite 4.1 3B— what is it used for?

It works in the domain of Language, and is recorded as handling the task of 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.

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.