Gemma 1.1 7B Instruct TPS calculator

Open weights Google 8.5B parameters February 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

306 cards that can run it

818 cards we hold specifications for

Smallest card that fits

P102-101

10 GB · Q4_K_M · 31.2 tok/s

Fastest card

B200

397 tok/s · 180 GB

Which GPUs can run Gemma 1.1 7B Instruct?

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.

306 cards match

Calculating
Needs Quantisation Fit
397 tok/s

337–476

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 12.8 GB Q8_0 Comfortable
397 tok/s

337–476

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 12.8 GB Q8_0 Comfortable
317 tok/s

190–507 · low confidence

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

190–507 · low confidence

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

152–405 · low confidence

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

206–291

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 12.8 GB Q8_0 Comfortable
243 tok/s

206–291

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 12.8 GB Q8_0 Comfortable
232 tok/s

139–371 · low confidence

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

124–330 · low confidence

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

124–330 · low confidence

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

124–330 · low confidence

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

166–234

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 12.8 GB Q8_0 Comfortable
179 tok/s

152–214

CMP 170HX 10 GB NVIDIA 10 GB 1,560 GB/s Sep 2021 8.8 GB Q4_K_M Tight
167 tok/s

142–200

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 12.8 GB Q8_0 Comfortable
167 tok/s

142–200

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 12.8 GB Q8_0 Comfortable
167 tok/s

142–200

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 12.8 GB Q8_0 Comfortable
167 tok/s

142–200

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 12.8 GB Q8_0 Comfortable
167 tok/s

142–200

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 12.8 GB Q8_0 Comfortable
127 tok/s

76–203 · low confidence

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

76–203 · low confidence

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

63–169 · low confidence

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

62–166 · low confidence

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

86–121

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 12.8 GB Q8_0 Comfortable
101 tok/s

86–121

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 12.8 GB Q8_0 Comfortable
101 tok/s

86–121

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 12.8 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
Google
Organisation type
Industry
Country
United States of America
Published
24 February 2024
Authors
Gemma Team, Thomas Mesnard, Cassidy Hardin, Robert Dadashi, Surya Bhupatiraju, Laurent Sifre, Morgane Rivière, Mihir Sanjay Kale, Juliette Love, Pouya Tafti, Léonard Hussenot and et al.

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

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
8.5B

Safetensors Model size 8.54B params

Training data
6,000,000,000,000 tokens

"These models were trained on a dataset of text data that includes a wide variety of sources, totaling 6 trillion 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
3.1 × 10²³ FLOP

6ND = 6*6000000000000*8540000000=3.0744e+23

How it was established
Operation counting

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
Google TPU v5e

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

https://huggingface.co/google/gemma-1.1-7b-it "This repository is publicly accessible, but you have to accept the conditions to access its files and content."

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.

Last updated
28 November 2025

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

P102-101

Memory needed

8.8 GB

Fastest

397 tok/s

Gemma 1.1 7B Instruct reaches a parameter count of 8.5B. 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: 306.

The entry point is P102-101, with a memory capacity of 10 GB, running it at a compression of Q4_K_M and producing around 31.2 tokens per second.

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

Background

Gemma 1.1 7B Instruct was published by Google, in the country recorded as United States of America, during February 2024. 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, Question answering.

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.

Reading the throughput figures

Half the cards that hold it manage more than 30.4 tokens per second. Exceeding reading speed outright: 282 of them.

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.

Because the architecture is recorded, the memory column is derived rather than estimated.

How it was trained

Producing it required arithmetic totalling around 3.1 × 10²³ FLOP, on hardware recorded as Google TPU v5e. That figure measures what producing the model cost, and has no bearing on how fast it answers.

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

Step by step

How to choose a GPU for Gemma 1.1 7B Instruct

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

  1. 01

    Check what it needs before anything else

    Every card here has been checked against Gemma 1.1 7B Instruct, needing around 8.8 GB at a compression of Q4_K_M. That figure, not the headline performance of a card, is what decides whether it runs.

  2. 02

    Set the context length you will work at

    The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect, because at long context a card that handles short questions easily can be dropped by Gemma 1.1 7B Instruct.

  3. 03

    Decide how much compression you will accept

    Compression is what makes a model fit smaller cards, at some cost in accuracy, reaching a compression of Q4_K_M 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 Gemma 1.1 7B Instruct. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 397 tok/s.

  5. 05

    Check the fit verdict before buying

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

    Open the card you have settled on

    Every card name links to its own page, which runs the same calculation across the whole model catalogue. A card is usually bought for more than one model, so it is worth a look before buying for Gemma 1.1 7B Instruct.

Answers

Gemma 1.1 7B Instruct — common questions

01

Gemma 1.1 7B Instruct— how many parameters does it have?

It has a parameter count of 8.5B. Safetensors Model size 8.54B params. 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.

02

Gemma 1.1 7B Instruct— who created it?

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

03

Gemma 1.1 7B Instruct— when was it released?

It was published in February 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.

04

Gemma 1.1 7B Instruct— what is it used for?

It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Question answering. These are the areas it was designed around; they describe intent rather than a hard boundary.

05

Gemma 1.1 7B Instruct— 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.

06

Gemma 1.1 7B Instruct— how much compute was used to train it?

Training consumed around 3.1 × 10²³ FLOP, on hardware recorded as Google TPU v5e. 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.

07

Gemma 1.1 7B Instruct— can I run it if it does not fit in my GPU?

Only by offloading, which is usually a false economy: the part held in system memory drags the whole thing down. The nearest miss we calculate falls short by 1.6 GB. Every figure here assumes the whole model is resident on the card.

08

Gemma 1.1 7B Instruct— would two GPUs run it faster?

Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 306. So a second card is rarely the answer here.

09

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

10

Gemma 1.1 7B Instruct— 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: 337–476 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

11

Gemma 1.1 7B Instruct— what GPU do I need to run it?

The smallest card in our catalogue that holds it is P102-101, with a memory capacity of 10 GB. It runs the model at a compression of Q4_K_M using about 8.8 GB, and produces roughly 31.2 tokens per second. The number of cards able to run it in total: 306.

12

Gemma 1.1 7B Instruct— how fast is it on a GPU?

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

13

Gemma 1.1 7B Instruct— how much VRAM does it need?

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

14

Gemma 1.1 7B Instruct— 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 Q5_K_M, using about 9.8 GB and generating roughly 80.8 tokens per second. The fit is tight.

15

Gemma 1.1 7B Instruct— 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 12.8 GB and generating roughly 56.0 tokens per second. The fit is tight.

16

Gemma 1.1 7B Instruct— 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 12.8 GB and generating roughly 66.5 tokens per second. The fit is comfortable.

17

Gemma 1.1 7B Instruct— 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.

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.