ViT-Huge/14 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 · Q8_0 · 58.3 tok/s
Fastest card
B200
5,361 tok/s · 180 GB
Which GPUs can run ViT-Huge/14?
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 | |||||
|---|---|---|---|---|---|---|---|
|
5,361
tok/s
3,217–8,578 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.4 GB | Q8_0 | Comfortable |
|
5,361
tok/s
3,217–8,578 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.4 GB | Q8_0 | Comfortable |
|
4,281
tok/s
2,569–6,850 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.4 GB | Q8_0 | Comfortable |
|
4,281
tok/s
2,569–6,850 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.4 GB | Q8_0 | Comfortable |
|
3,424
tok/s
2,054–5,478 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.4 GB | Q8_0 | Comfortable |
|
3,277
tok/s
1,966–5,243 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.4 GB | Q8_0 | Comfortable |
|
3,277
tok/s
1,966–5,243 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.4 GB | Q8_0 | Comfortable |
|
3,136
tok/s
1,882–5,018 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.4 GB | Q8_0 | Comfortable |
|
2,783
tok/s
1,670–4,453 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.4 GB | Q8_0 | Comfortable |
|
2,783
tok/s
1,670–4,453 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.4 GB | Q8_0 | Comfortable |
|
2,783
tok/s
1,670–4,453 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.4 GB | Q8_0 | Comfortable |
|
2,640
tok/s
1,584–4,225 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.4 GB | Q8_0 | Comfortable |
|
2,252
tok/s
1,351–3,603 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.4 GB | Q8_0 | Comfortable |
|
2,252
tok/s
1,351–3,603 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.4 GB | Q8_0 | Comfortable |
|
2,252
tok/s
1,351–3,603 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.4 GB | Q8_0 | Comfortable |
|
2,252
tok/s
1,351–3,603 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.4 GB | Q8_0 | Comfortable |
|
2,252
tok/s
1,351–3,603 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.4 GB | Q8_0 | Comfortable |
|
1,714
tok/s
1,029–2,743 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.4 GB | Q8_0 | Comfortable |
|
1,714
tok/s
1,029–2,743 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.4 GB | Q8_0 | Comfortable |
|
1,429
tok/s
857–2,286 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.4 GB | Q8_0 | Comfortable |
|
1,398
tok/s
839–2,237 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.4 GB | Q8_0 | Comfortable |
|
1,367
tok/s
820–2,187 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.4 GB | Q8_0 | Comfortable |
|
1,367
tok/s
820–2,187 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.4 GB | Q8_0 | Comfortable |
|
1,367
tok/s
820–2,187 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.4 GB | Q8_0 | Comfortable |
|
1,367
tok/s
820–2,187 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.4 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 Brain,Google Research
- Organisation type
- Industry,Industry
- Country
- United States of America
- Published
- 22 October 2020
- Authors
- Alexey Dosovitskiy, Lucas Beyer, Alexander Kolesnikov, Dirk Weissenborn, Xiaohua Zhai, Thomas Unterthiner, Mostafa Dehghani, Matthias Minderer, Georg Heigold, Sylvain Gelly, Jakob Uszkoreit, Neil Houlsby
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision
- Task
- Image representation
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
- 632M
- Training data
- 303,000,000 tokens
- Epochs
- 14
Table 1 https://arxiv.org/pdf/2010.11929.pdf
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
- 4.3 × 10²¹ FLOP
- How it was established
- Hardware
Table 6: 4.262e21 FLOPs Agrees with Table 2 (2.5k TPUv3-core days), if MFU is around 0.32. 2500 * 24 * 3600 * (0.5 * 1.23e14) * 0.32 = 4.25e21
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 v3
- Chip-hours
- 30,000
- Hardware utilisation
- MFU 32.1%
- Compute cost
- $6,724
Stated FLOPs to train is 4.262e21 Training used 2500 TPUv3-core-days, so at max utilization: 2500/2 * 24 * 3600 s * 1.23e14 FLOP/s = 1.328e22 FLOPs MFU = 4.261e21 / 1.328e22 = 0.3208
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)
- Training code
- Open source
Apache-2.0 license https://github.com/google-research/vision_transformer
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Why it is tracked
- Highly cited
- Record confidence
- Confident
- Citations
- 62,651
Sources
Where this record came from and when it was last checked.
- Reference
- An Image is Worth 16x16 Words: Transformers for Image Recognition at Scale
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run ViT-Huge/14
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 5,361 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 5,361 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 4,281 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 4,281 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 3,424 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 3,277 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 3,277 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 3,136 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 2,783 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 2,783 tok/s
The smallest GPUs that still run ViT-Huge/14
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.4 GB · Q8_0 · comfortable 64.3 tok/s
- 02 RTX A400 4 GB · needs 1.4 GB · Q8_0 · comfortable 64.3 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.4 GB · Q8_0 · comfortable 85.8 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.4 GB · Q8_0 · comfortable 129 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.4 GB · Q8_0 · comfortable 22.9 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.4 GB · Q8_0 · comfortable 66.9 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.4 GB · Q8_0 · comfortable 75.3 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.4 GB · Q8_0 · comfortable 66.9 tok/s
- 09 Arc A310 4 GB · needs 1.4 GB · Q8_0 · comfortable 54.0 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.4 GB · Q8_0 · comfortable 55.8 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla C1080
Memory needed
1.4 GB
Fastest
5,361 tok/s
ViT-Huge/14 reaches a parameter count of 632M. 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 Q8_0 and producing around 58.3 tokens per second.
The fastest we calculate for it is B200, generating roughly 5,361 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
ViT-Huge/14 was published by Google Brain,Google Research, in the country recorded as United States of America, during October 2020. It comes out of an organisation categorised as industry,Industry.
It works in the domain of Vision, and is recorded as performing the task of image representation.
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.
How fast it runs, and why
The median result is around 150.5 tokens per second. Producing text faster than most people read it: 809 of them.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
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.
Training and provenance
Producing it required arithmetic totalling around 4.3 × 10²¹ FLOP, on hardware recorded as Google TPU v3. That figure measures what producing the model cost, and has no bearing on how fast it answers.
The training set ran to roughly 303,000,000 tokens of text.
Its inclusion criterion: highly cited.
Step by step
How to choose a GPU for ViT-Huge/14
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
Start from what it actually needs, which is the requirement of ViT-Huge/14, needing around 1.4 GB at a compression of Q8_0. That figure, not the headline performance of a card, is what decides whether it runs.
-
02
Match the context to your actual use
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 ViT-Huge/14.
-
03
Choose how far you will compress it
Each card runs the least-compressed copy it can hold, reaching a compression of Q8_0 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
Compare tokens per second, not specifications
Ranking by tokens per second follows memory bandwidth rather than core counts, for ViT-Huge/14. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 5,361 tok/s.
-
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 ViT-Huge/14. 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
Open the card you have settled on
Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond ViT-Huge/14.
Answers
ViT-Huge/14 — common questions
ViT-Huge/14— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 5,361 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: 809.
ViT-Huge/14— how much VRAM does it need?
It needs about 1.4 GB at a compression of Q8_0, 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.
ViT-Huge/14— 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 1.4 GB and generating roughly 999 tokens per second. The fit is comfortable.
ViT-Huge/14— 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 1.4 GB and generating roughly 611 tokens per second. The fit is comfortable.
ViT-Huge/14— 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 1.4 GB and generating roughly 757 tokens per second. The fit is comfortable.
ViT-Huge/14— 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 1.4 GB and generating roughly 898 tokens per second. The fit is comfortable.
ViT-Huge/14— 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.
ViT-Huge/14— how many parameters does it have?
It has a parameter count of 632M. Table 1 https://arxiv.org/pdf/2010.11929.pdf. 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.
ViT-Huge/14— who created it?
It was published by Google Brain,Google Research, based in United States of America, an organisation categorised as industry,Industry.
ViT-Huge/14— when was it released?
It was published in October 2020. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
ViT-Huge/14— what is it used for?
It works in the domain of Vision, and is recorded as handling the task of image representation. 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.
ViT-Huge/14— 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.
ViT-Huge/14— how much compute was used to train it?
Training consumed around 4.3 × 10²¹ FLOP, on hardware recorded as Google TPU v3. 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.
ViT-Huge/14— 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. Every figure here assumes the whole model is resident on the card.
ViT-Huge/14— 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.
ViT-Huge/14— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
ViT-Huge/14— 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: 3,217–8,578 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
ViT-Huge/14— 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 Q8_0 using about 1.4 GB, and produces roughly 58.3 tokens per second. The number of cards able to run it in total: 818.
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.