Gemma 2 2B 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 · Q6_K · 20.6 tok/s
Fastest card
B200
1,303 tok/s · 180 GB
Which GPUs can run Gemma 2 2B?
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,303
tok/s
1,108–1,564 |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 3.9 GB | Q8_0 | Comfortable |
|
1,303
tok/s
1,108–1,564 |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 3.9 GB | Q8_0 | Comfortable |
|
1,041
tok/s
624–1,665 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 3.9 GB | Q8_0 | Comfortable |
|
1,041
tok/s
624–1,665 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 3.9 GB | Q8_0 | Comfortable |
|
832
tok/s
499–1,332 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 3.9 GB | Q8_0 | Comfortable |
|
797
tok/s
677–956 |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 3.9 GB | Q8_0 | Comfortable |
|
797
tok/s
677–956 |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 3.9 GB | Q8_0 | Comfortable |
|
762
tok/s
457–1,220 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 3.9 GB | Q8_0 | Comfortable |
|
677
tok/s
406–1,083 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 3.9 GB | Q8_0 | Comfortable |
|
677
tok/s
406–1,083 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 3.9 GB | Q8_0 | Comfortable |
|
677
tok/s
406–1,083 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 3.9 GB | Q8_0 | Comfortable |
|
642
tok/s
546–770 |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
547
tok/s
465–657 |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
547
tok/s
465–657 |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 3.9 GB | Q8_0 | Comfortable |
|
547
tok/s
465–657 |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
547
tok/s
465–657 |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
547
tok/s
465–657 |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
417
tok/s
250–667 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 3.9 GB | Q8_0 | Comfortable |
|
417
tok/s
250–667 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 3.9 GB | Q8_0 | Comfortable |
|
347
tok/s
208–556 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 3.9 GB | Q8_0 | Comfortable |
|
340
tok/s
204–544 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 3.9 GB | Q8_0 | Comfortable |
|
332
tok/s
282–399 |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 3.9 GB | Q8_0 | Comfortable |
|
332
tok/s
282–399 |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 3.9 GB | Q8_0 | Comfortable |
|
332
tok/s
282–399 |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 3.9 GB | Q8_0 | Comfortable |
|
332
tok/s
282–399 |
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
- Google DeepMind
- Organisation type
- Industry
- Country
- United States of America
- Published
- 24 June 2024
- Authors
- Gemma Team, Google DeepMind
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Chat, Code 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
- 2.6B
- Training data
- 2,000,000,000,000 tokens
"the 2.6B on 2 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
- How it was established
- Operation counting
"For the 2.6B model, we train on a 2x16x16 configuration of TPUv5e, totaling 512 chips" 6ND = 6 FLOP / token / parameter * 2600000000 parameters * 2000000000000 tokens = 3.12e+22 FLOP
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
- Chips used
- 512
- Power draw
- 227.4 kW
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-2-2b Gemma 2 is available under our commercially-friendly Gemma license, giving developers and researchers the ability to share and commercialize their innovations.
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
Sources
Where this record came from and when it was last checked.
- Reference
- Gemma 2 offers best-in-class performance, runs at incredible speed across different hardware and easily integrates with other AI tools.
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Gemma 2 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.
- 01 B300 288 GB · 8,000 GB/s · Q8_0 1,303 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 1,303 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 1,041 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 1,041 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 832 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 797 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 797 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 762 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 677 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 677 tok/s
The smallest GPUs that still run Gemma 2 2B
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 3.3 GB · Q6_K · tight 22.7 tok/s
- 02 RTX A400 4 GB · needs 3.3 GB · Q6_K · tight 22.7 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 3.3 GB · Q6_K · tight 30.3 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 3.3 GB · Q6_K · tight 45.4 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 3.3 GB · Q6_K · tight 8.1 tok/s
- 06 Radeon RX 6450M 4 GB · needs 3.3 GB · Q6_K · tight 23.6 tok/s
- 07 Radeon RX 6550M 4 GB · needs 3.3 GB · Q6_K · tight 26.6 tok/s
- 08 Radeon RX 6550S 4 GB · needs 3.3 GB · Q6_K · tight 23.6 tok/s
- 09 Arc A310 4 GB · needs 3.3 GB · Q6_K · tight 19.1 tok/s
- 10 Arc Pro A30M 4 GB · needs 3.3 GB · Q6_K · tight 19.7 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Tesla C1080
Memory needed
3.3 GB
Fastest
1,303 tok/s
Gemma 2 2B reaches a parameter count of 2.6B. 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.
The smallest card that holds it is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q6_K and producing around 20.6 tokens per second.
The quickest result comes from B200, generating roughly 1,303 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
Gemma 2 2B was published by Google DeepMind, in the country recorded as United States of America, during June 2024. The category the publisher falls under is industry.
It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Chat, Code generation, Question answering.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.
How fast it runs, and why
Half the cards that hold it manage more than 41.4 tokens per second. Producing text faster than most people read it: 786 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 attention layout is on file, so the memory figures are computed exactly rather than approximated.
What went into building it
The training run consumed about 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.
It was trained on a corpus of about 2,000,000,000,000 tokens of text.
Step by step
How to choose a GPU for Gemma 2 2B
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 Gemma 2 2B, needing around 3.3 GB at a compression of Q6_K. 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, because at long context a card that handles short questions easily can be dropped by Gemma 2 2B.
-
03
Decide how much compression you will accept
The quantisation column varies by card, because a bigger card holds a more accurate copy, 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.
-
04
Rank by throughput rather than spec sheet
Ranking by tokens per second follows memory bandwidth rather than core counts, for Gemma 2 2B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 1,303 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage it from those with room to spare, in the case of Gemma 2 2B. 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.
-
06
Check the card from the other side
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 2 2B.
Answers
Gemma 2 2B — common questions
Gemma 2 2B— why does the quantisation differ between cards?
A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 2. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Gemma 2 2B— how accurate are these speed estimates?
These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 1,108–1,564 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Gemma 2 2B— 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.3 GB, and produces roughly 20.6 tokens per second. The number of cards able to run it in total: 818.
Gemma 2 2B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 1,303 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: 786.
Gemma 2 2B— how much VRAM does it need?
It needs about 3.3 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.
Gemma 2 2B— 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 243 tokens per second. The fit is comfortable.
Gemma 2 2B— 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 149 tokens per second. The fit is comfortable.
Gemma 2 2B— 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 184 tokens per second. The fit is comfortable.
Gemma 2 2B— 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 218 tokens per second. The fit is comfortable.
Gemma 2 2B— 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.
Gemma 2 2B— how many parameters does it have?
It has a parameter count of 2.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.
Gemma 2 2B— who created it?
It was published by Google DeepMind, based in United States of America, an organisation categorised as industry.
Gemma 2 2B— when was it released?
It was published in June 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.
Gemma 2 2B— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Chat, Code generation, Question answering. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Gemma 2 2B— 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.
Gemma 2 2B— 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.
Gemma 2 2B— can I run it if it does not fit in my GPU?
It can be split between the card and system memory, but it generates painfully slowly that way. Every figure here assumes the whole model is resident on the card.
Gemma 2 2B— 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: 818. So a second card is rarely the answer here.
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.