Llama 3.2 11B 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
Xeon Phi 5110P
8 GB · Q4_K_M · 19.2 tok/s
Fastest card
B200
320 tok/s · 180 GB
Which GPUs can run Llama 3.2 11B?
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.
509 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
320
tok/s
192–511 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 12.0 GB | Q8_0 | Comfortable |
|
320
tok/s
192–511 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 12.0 GB | Q8_0 | Comfortable |
|
255
tok/s
153–408 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 12.0 GB | Q8_0 | Comfortable |
|
255
tok/s
153–408 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 12.0 GB | Q8_0 | Comfortable |
|
204
tok/s
122–327 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 12.0 GB | Q8_0 | Comfortable |
|
195
tok/s
117–313 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 12.0 GB | Q8_0 | Comfortable |
|
195
tok/s
117–313 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 12.0 GB | Q8_0 | Comfortable |
|
187
tok/s
112–299 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 12.0 GB | Q8_0 | Comfortable |
|
166
tok/s
100–266 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 12.0 GB | Q8_0 | Comfortable |
|
166
tok/s
100–266 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 12.0 GB | Q8_0 | Comfortable |
|
166
tok/s
100–266 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 12.0 GB | Q8_0 | Comfortable |
|
157
tok/s
94–252 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 12.0 GB | Q8_0 | Comfortable |
|
137
tok/s
82–220 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 7.1 GB | Q4_K_M | Tight |
|
134
tok/s
81–215 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 12.0 GB | Q8_0 | Comfortable |
|
134
tok/s
81–215 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 12.0 GB | Q8_0 | Comfortable |
|
134
tok/s
81–215 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 12.0 GB | Q8_0 | Comfortable |
|
134
tok/s
81–215 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 12.0 GB | Q8_0 | Comfortable |
|
134
tok/s
81–215 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 12.0 GB | Q8_0 | Comfortable |
|
111
tok/s
67–178 · low confidence |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.3 GB | Q5_K_M | Tight |
|
102
tok/s
61–164 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 12.0 GB | Q8_0 | Comfortable |
|
102
tok/s
61–164 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 12.0 GB | Q8_0 | Comfortable |
|
85.2
tok/s
51–136 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 12.0 GB | Q8_0 | Comfortable |
|
83.4
tok/s
50–133 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 12.0 GB | Q8_0 | Comfortable |
|
81.5
tok/s
49–130 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 12.0 GB | Q8_0 | Comfortable |
|
81.5
tok/s
49–130 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 12.0 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
- Meta AI
- Organisation type
- Industry
- Country
- United States of America
- Published
- 24 September 2024
- Authors
- Meta AI
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Multimodal, Vision, Language
- Task
- Visual question answering, Image captioning, Object detection
- Base model
- Llama 3.1-8B
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
- 10.6B
- Training data
- tokens
https://huggingface.co/meta-llama/Llama-3.2-11B-Vision
Since the model can also be used for image captioning, I assume the dataset size is measured in numbers of image-caption pairs (https://docs.google.com/document/d/1XWLyMzcVfDv4eFQX3yPgM8MZ3_Q1phtIFz9GKv4_KaM/edit?tab=t.0#heading=h.ny4fw3njk98p). ""Llama 3.2-Vision was pretrained on 6B image and text pairs" (https://github.com/meta-llama/llama-models/blob/main/models/llama3_2/MODEL_CARD_VISION.md#training-data).
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
- 5.8 × 10²³ FLOP
- How it was established
- Hardware
- Fine-tuning compute
- 3.5 × 10²³ FLOP
Tensor type is BF16 (https://huggingface.co/meta-llama/Llama-3.2-11B-Vision-Instruct). “Training utilized a cumulative of 2.02M GPU hours of computation on H100-80GB (TDP of 700W) type hardware, per the table below. Training time is the total GPU time required for training each model and power consumption is the peak power capacity per GPU device used, adjusted for power usage efficiency… Training time: Stage 1 pretraining: 147K H100 hours Stage 2 annealing: 98K H100 hours SFT: 896 H100 hours R…
147000+98000+896+224 GPU-hours => 246120 GPU-hours * 60 * 60 * 989e12 FLOP * 0.4 (utilization) = 3.5e23 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
- NVIDIA H100 SXM5 80GB
- Chip-hours
- 246,120
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
LLAMA 3.2 COMMUNITY LICENSE AGREEMENT https://github.com/meta-llama/llama-models/blob/main/models/llama3_2/LICENSE
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
- Why it is tracked
- Significant use
- Record confidence
- Confident
1,019,539 downloads on HuggingFace last month at time of writing (https://huggingface.co/meta-llama/Llama-3.2-11B-Vision-Instruct).
Sources
Where this record came from and when it was last checked.
- Reference
- Llama 3.2: Revolutionizing edge AI and vision with open, customizable models
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Llama 3.2 11B
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 320 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 320 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 255 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 255 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 204 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 195 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 195 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 187 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 166 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 166 tok/s
The smallest GPUs that still run Llama 3.2 11B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Radeon RX 7400 8 GB · needs 7.1 GB · Q4_K_M · tight 20.7 tok/s
- 02 Radeon RX 9060 8 GB · needs 7.1 GB · Q4_K_M · tight 23.2 tok/s
- 03 GeForce RTX 5050 8 GB · needs 7.1 GB · Q4_K_M · tight 29.5 tok/s
- 04 GeForce RTX 5050 Mobile 8 GB · needs 7.1 GB · Q4_K_M · tight 35.4 tok/s
- 05 Radeon RX 9060 XT 8 GB 8 GB · needs 7.1 GB · Q4_K_M · tight 23.2 tok/s
- 06 GeForce RTX 5060 Mobile 8 GB · needs 7.1 GB · Q4_K_M · tight 35.4 tok/s
- 07 GeForce RTX 5060 8 GB · needs 7.1 GB · Q4_K_M · tight 41.3 tok/s
- 08 GeForce RTX 5060 Ti 8 GB 8 GB · needs 7.1 GB · Q4_K_M · tight 41.3 tok/s
- 09 GeForce RTX 5070 Mobile 8 GB · needs 7.1 GB · Q4_K_M · tight 35.4 tok/s
- 10 Radeon RX 7650 GRE 8 GB · needs 7.1 GB · Q4_K_M · tight 20.7 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Xeon Phi 5110P
Memory needed
7.1 GB
Fastest
320 tok/s
Llama 3.2 11B reaches a parameter count of 10.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: 509.
The smallest card that holds it is Xeon Phi 5110P, with a memory capacity of 8 GB, running it at a compression of Q4_K_M and producing around 19.2 tokens per second.
At the other end sits B200, generating roughly 320 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
Llama 3.2 11B was published by Meta AI, in the country recorded as United States of America, during September 2024. The category the publisher falls under is industry.
It works in the domain of Multimodal, Vision, Language, and is recorded as performing the task of visual question answering, Image captioning, Object detection.
Rather than being trained from scratch, it is derived from Llama 3.1-8B. That is why it shares the base 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.
How fast it runs, and why
The median result is around 20.7 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 462 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.
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
Training it took a computation budget of roughly 5.8 × 10²³ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The reason it appears in this catalogue at all: significant use.
Step by step
How to choose a GPU for Llama 3.2 11B
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
Start from what it actually needs, which is the requirement of Llama 3.2 11B, needing around 7.1 GB at a compression of Q4_K_M. No amount of processing power compensates for a card that cannot hold it.
-
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 a card that seemed fine stops fitting Llama 3.2 11B.
-
03
Set a quality floor
Each card runs the least-compressed copy it can hold, 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.
-
04
Rank by throughput rather than spec sheet
The speed ordering is effectively an ordering by memory bandwidth, for Llama 3.2 11B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 320 tok/s.
-
05
Check the fit verdict before buying
Tight means it loads and works with no room to raise the context later, in the case of Llama 3.2 11B. 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
See what else that card runs
Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond Llama 3.2 11B.
Answers
Llama 3.2 11B — common questions
Llama 3.2 11B— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Xeon Phi 5110P, with a memory capacity of 8 GB. It runs the model at a compression of Q4_K_M using about 7.1 GB, and produces roughly 19.2 tokens per second. The number of cards able to run it in total: 509.
Llama 3.2 11B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 320 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: 462.
Llama 3.2 11B— how much VRAM does it need?
It needs about 7.1 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.
Llama 3.2 11B— 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 Q4_K_M, using about 7.1 GB and generating roughly 137 tokens per second. The fit is tight.
Llama 3.2 11B— 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 Q6_K, using about 9.6 GB and generating roughly 53.0 tokens per second. The fit is tight.
Llama 3.2 11B— 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.0 GB and generating roughly 45.2 tokens per second. The fit is tight.
Llama 3.2 11B— 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.0 GB and generating roughly 53.5 tokens per second. The fit is comfortable.
Llama 3.2 11B— 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.
Llama 3.2 11B— how many parameters does it have?
It has a parameter count of 10.6B. https://huggingface.co/meta-llama/Llama-3.2-11B-Vision. 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.
Llama 3.2 11B— who created it?
It was published by Meta AI, based in United States of America, an organisation categorised as industry.
Llama 3.2 11B— when was it released?
It was published in September 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.
Llama 3.2 11B— what is it used for?
It works in the domain of Multimodal, Vision, Language, and is recorded as handling the task of visual question answering, Image captioning, Object detection. These are the areas it was designed around; they describe intent rather than a hard boundary.
Llama 3.2 11B— 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.
Llama 3.2 11B— how much compute was used to train it?
Training consumed around 5.8 × 10²³ FLOP, on hardware recorded as 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.
Llama 3.2 11B— 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. The nearest miss we calculate falls short by 1.7 GB. Every figure here assumes the whole model is resident on the card.
Llama 3.2 11B— 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: 509. So a second card is rarely the answer here.
Llama 3.2 11B— why does the quantisation differ between cards?
Each card is shown running the least-compressed copy it can hold. The number of distinct compression levels across the cards that fit it: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
Llama 3.2 11B— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 192–511 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
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.