Gemma 3 1B 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
Smallest card that fits
Tesla C1080
4 GB · Q8_0 · 36.9 tok/s
Fastest card
B200
3,388 tok/s · 180 GB
Which GPUs can run Gemma 3 1B?
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 | |||||
|---|---|---|---|---|---|---|---|
|
3,388
tok/s
2,880–4,066 |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.8 GB | Q8_0 | Comfortable |
|
3,388
tok/s
2,880–4,066 |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.8 GB | Q8_0 | Comfortable |
|
2,706
tok/s
1,623–4,329 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.8 GB | Q8_0 | Comfortable |
|
2,706
tok/s
1,623–4,329 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.8 GB | Q8_0 | Comfortable |
|
2,164
tok/s
1,298–3,462 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.8 GB | Q8_0 | Comfortable |
|
2,071
tok/s
1,760–2,485 |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.8 GB | Q8_0 | Comfortable |
|
2,071
tok/s
1,760–2,485 |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.8 GB | Q8_0 | Comfortable |
|
1,982
tok/s
1,189–3,171 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.8 GB | Q8_0 | Comfortable |
|
1,759
tok/s
1,055–2,815 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,759
tok/s
1,055–2,815 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,759
tok/s
1,055–2,815 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,669
tok/s
1,418–2,002 |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,423
tok/s
1,210–1,708 |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,423
tok/s
1,210–1,708 |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.8 GB | Q8_0 | Comfortable |
|
1,423
tok/s
1,210–1,708 |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,423
tok/s
1,210–1,708 |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,423
tok/s
1,210–1,708 |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.8 GB | Q8_0 | Comfortable |
|
1,084
tok/s
650–1,734 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.8 GB | Q8_0 | Comfortable |
|
1,084
tok/s
650–1,734 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.8 GB | Q8_0 | Comfortable |
|
903
tok/s
542–1,445 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.8 GB | Q8_0 | Comfortable |
|
884
tok/s
530–1,414 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.8 GB | Q8_0 | Comfortable |
|
864
tok/s
734–1,037 |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.8 GB | Q8_0 | Comfortable |
|
864
tok/s
734–1,037 |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.8 GB | Q8_0 | Comfortable |
|
864
tok/s
734–1,037 |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.8 GB | Q8_0 | Comfortable |
|
864
tok/s
734–1,037 |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.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 DeepMind
- Organisation type
- Industry
- Country
- United States of America
- Published
- 12 March 2025
- Authors
- Core contributors: Aishwarya Kamath, Johan Ferret, Shreya Pathak, Nino Vieillard, Ramona Merhej, Sarah Perrin, Tatiana Matejovicova, Alexandre Ramé, Morgane Rivière, Louis Rouillard, Thomas Mesnard, Geoffrey Cideron, Jean-bastien Grill, Sabela Ramos, Edouard Yvinec, Michelle Casbon, Etienne Pot, Ivo Penchev, Gaël Liu, Francesco Visin, Kathleen Kenealy, Lucas Beyer, Xiaohai Zhai, Anton Tsitsulin, R…
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, Chat, Quantitative reasoning, Code generation, Mathematical reasoning
- Base model
- SigLIP 400M
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
- 1B
- Training data
- 2,000,000,000,000 tokens
Embedding Parameters: 302M Non-embedding Parameters: 698M
2T
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.2 × 10²² FLOP
- How it was established
- Operation counting
6ND = 6 * 1B parameters * 2T training tokens = 1.2 × 10^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
- 226.1 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
- Hugging Face
https://huggingface.co/google/gemma-3-1b-it Gemma 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
Sources
Where this record came from and when it was last checked.
- Reference
- Gemma 3 Technical Report
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs for Gemma 3 1B
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 3,388 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 3,388 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 2,706 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 2,706 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 2,164 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 2,071 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 2,071 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 1,982 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 1,759 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 1,759 tok/s
The smallest GPUs that still run Gemma 3 1B
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.8 GB · Q8_0 · comfortable 40.7 tok/s
- 02 RTX A400 4 GB · needs 1.8 GB · Q8_0 · comfortable 40.7 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.8 GB · Q8_0 · comfortable 54.2 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.8 GB · Q8_0 · comfortable 81.3 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.8 GB · Q8_0 · comfortable 14.5 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.8 GB · Q8_0 · comfortable 42.3 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.8 GB · Q8_0 · comfortable 47.6 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.8 GB · Q8_0 · comfortable 42.3 tok/s
- 09 Arc A310 4 GB · needs 1.8 GB · Q8_0 · comfortable 34.1 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.8 GB · Q8_0 · comfortable 35.2 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Tesla C1080
Memory needed
1.8 GB
Fastest
3,388 tok/s
Gemma 3 1B is small enough at 1B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The smallest card that holds it is the Tesla C1080 with 4 GB, running it at Q8_0 and producing around 36.9 tokens per second.
The quickest result comes from a B200 at around 3,388 tokens per second — its 8,000 GB/s of bandwidth is what buys that.
Background
Gemma 3 1B was published by Google DeepMind, in United States of America, in March 2025. industry is the category the publisher falls under.
It works in Language, and is recorded as doing language modeling/generation, Question answering, Translation, Chat, Quantitative reasoning, Code generation, Mathematical reasoning.
It builds on SigLIP 400M, which is why it shares that model's general shape and size.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. It is published under the google organisation on Hugging Face.
Reading the throughput figures
Across every card that can run it, the middle of the range is about 95.1 tokens per second, and 806 of them clear the ten tokens per second that roughly matches reading speed.
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.
What went into building it
Producing it required around 1.2 × 10²² FLOP of arithmetic, on Google TPU v5e, which is a statement about the training budget rather than about inference.
Around 2,000,000,000,000 tokens went into training it.
Step by step
How to choose a GPU for Gemma 3 1B
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
Every card here has been checked against Gemma 3 1B — around 1.8 GB at Q8_0. Capacity is the gate — a card either holds it or it does not.
-
02
Set the context length you will work at
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for Gemma 3 1B.
-
03
Choose how far you will compress it
The quantisation column varies by card, because a bigger card holds a more accurate copy of Gemma 3 1B — Q8_0 on the smallest card that fits. Set a floor to hold the comparison at one level.
-
04
Sort by speed
Ranking by tokens per second for Gemma 3 1B follows memory bandwidth, not core counts, which is why the B200 tops it at 3,388 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage Gemma 3 1B from those with room to spare. Buy for the second if the context might grow.
-
06
Check the card from the other side
Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond Gemma 3 1B.
Answers
Gemma 3 1B — common questions
How much compute was used to train Gemma 3 1B?
Around 1.2 × 10²² FLOP, on 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.
Can I run Gemma 3 1B if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down. Our figures for Gemma 3 1B assume it is fully resident.
Would two GPUs run Gemma 3 1B faster?
A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run Gemma 3 1B alone, the case for pairing is weak.
Why does the quantisation differ between cards for Gemma 3 1B?
Each card is shown running the least-compressed copy it can hold, and Gemma 3 1B appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these Gemma 3 1B speed estimates?
These are estimates with real error bars. The fastest result here, 2,880–4,066 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 Gemma 3 1B?
The smallest card in our catalogue that holds Gemma 3 1B is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.8 GB, and produces roughly 36.9 tokens per second. 818 cards in total can run it.
How fast is Gemma 3 1B on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 3,388 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 806 of the cards that can run Gemma 3 1B clear that.
How much VRAM does Gemma 3 1B need?
About 1.8 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 Gemma 3 1B on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.8 GB and generating roughly 631 tokens per second — a comfortable fit.
Can I run Gemma 3 1B on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.8 GB and generating roughly 386 tokens per second — a comfortable fit.
Can I run Gemma 3 1B on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.8 GB and generating roughly 479 tokens per second — a comfortable fit.
Can I run Gemma 3 1B on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.8 GB and generating roughly 568 tokens per second — a comfortable fit.
Is Gemma 3 1B open source?
Its weights are published, so Gemma 3 1B 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 Gemma 3 1B have?
Gemma 3 1B has 1B parameters. Embedding Parameters: 302M Non-embedding Parameters: 698M. 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 Gemma 3 1B?
Gemma 3 1B was published by Google DeepMind, based in United States of America, categorised as industry.
When was Gemma 3 1B released?
Gemma 3 1B was published in March 2025.
What is Gemma 3 1B used for?
Gemma 3 1B works in Language, and is recorded as handling language modeling/generation, Question answering, Translation, Chat, Quantitative reasoning, Code generation, Mathematical reasoning. These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download Gemma 3 1B?
Its weights are published under the google organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
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.