GPT-2 (774M) 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 · 47.6 tok/s
Fastest card
B200
4,378 tok/s · 180 GB
Which GPUs can run GPT-2 (774M)?
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 | |||||
|---|---|---|---|---|---|---|---|
|
4,378
tok/s
2,627–7,004 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.5 GB | Q8_0 | Comfortable |
|
4,378
tok/s
2,627–7,004 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.5 GB | Q8_0 | Comfortable |
|
3,496
tok/s
2,097–5,593 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.5 GB | Q8_0 | Comfortable |
|
3,496
tok/s
2,097–5,593 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.5 GB | Q8_0 | Comfortable |
|
2,796
tok/s
1,677–4,473 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.5 GB | Q8_0 | Comfortable |
|
2,676
tok/s
1,605–4,281 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.5 GB | Q8_0 | Comfortable |
|
2,676
tok/s
1,605–4,281 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.5 GB | Q8_0 | Comfortable |
|
2,561
tok/s
1,537–4,097 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.5 GB | Q8_0 | Comfortable |
|
2,273
tok/s
1,364–3,636 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.5 GB | Q8_0 | Comfortable |
|
2,273
tok/s
1,364–3,636 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.5 GB | Q8_0 | Comfortable |
|
2,273
tok/s
1,364–3,636 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.5 GB | Q8_0 | Comfortable |
|
2,156
tok/s
1,294–3,450 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.5 GB | Q8_0 | Comfortable |
|
1,839
tok/s
1,103–2,942 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.5 GB | Q8_0 | Comfortable |
|
1,839
tok/s
1,103–2,942 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.5 GB | Q8_0 | Comfortable |
|
1,839
tok/s
1,103–2,942 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.5 GB | Q8_0 | Comfortable |
|
1,839
tok/s
1,103–2,942 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.5 GB | Q8_0 | Comfortable |
|
1,839
tok/s
1,103–2,942 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.5 GB | Q8_0 | Comfortable |
|
1,400
tok/s
840–2,240 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.5 GB | Q8_0 | Comfortable |
|
1,400
tok/s
840–2,240 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.5 GB | Q8_0 | Comfortable |
|
1,167
tok/s
700–1,867 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.5 GB | Q8_0 | Comfortable |
|
1,142
tok/s
685–1,827 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.5 GB | Q8_0 | Comfortable |
|
1,116
tok/s
670–1,786 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.5 GB | Q8_0 | Comfortable |
|
1,116
tok/s
670–1,786 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.5 GB | Q8_0 | Comfortable |
|
1,116
tok/s
670–1,786 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.5 GB | Q8_0 | Comfortable |
|
1,116
tok/s
670–1,786 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.5 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
- OpenAI
- Organisation type
- Industry
- Country
- United States of America
- Published
- 14 February 2019
- Authors
- Alec Radford, Jeffrey Wu, Rewon Child, David Luan, Dario Amodei, Ilya Sutskever
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation
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
- 774M
- Training data
- 10,666,666,667 tokens
- Epochs
- 100
Note that the initial paper release stated GPT-2 large had 762M parameters. The official github repo notes that this was due to an error: https://github.com/openai/gpt-2?tab=readme-ov-file
40GB * 200*10^6 words per GB * 4/3 tokens per word = 10666666666.7 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
- 5 × 10²¹ FLOP
assuming 100 epochs (consistent with original GPT paper + reasoning from here: https://arxiv.org/pdf/1906.06669) 6 FLOP / token / parameter * 774*10^6 parameters * 10666666666.7 tokens * 100 epochs = 4.9536e+21 FLOP
The training run
What it physically took to train: which chips, how many, for how long, and what that drew from the wall.
- Compute cost
- $18,857
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
- Unreleased
modified MIT https://github.com/openai/gpt-2?tab=License-1-ov-file#readme
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Frontier model
- Yes
- Why it is tracked
- Highly cited
- Record confidence
- Speculative
- Citations
- 26,463
- Benchmark data
- GPT-2 (762M)
Sources
Where this record came from and when it was last checked.
- Reference
- Language Models are Unsupervised Multitask Learners
- Last updated
- 11 February 2026
The extremes
The ten fastest GPUs that run GPT-2 (774M)
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 4,378 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 4,378 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 3,496 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 3,496 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 2,796 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 2,676 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 2,676 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 2,561 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 2,273 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 2,273 tok/s
The smallest GPUs that still run GPT-2 (774M)
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.5 GB · Q8_0 · comfortable 52.5 tok/s
- 02 RTX A400 4 GB · needs 1.5 GB · Q8_0 · comfortable 52.5 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.5 GB · Q8_0 · comfortable 70.0 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.5 GB · Q8_0 · comfortable 105 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.5 GB · Q8_0 · comfortable 18.7 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.5 GB · Q8_0 · comfortable 54.6 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.5 GB · Q8_0 · comfortable 61.5 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.5 GB · Q8_0 · comfortable 54.6 tok/s
- 09 Arc A310 4 GB · needs 1.5 GB · Q8_0 · comfortable 44.1 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.5 GB · Q8_0 · comfortable 45.5 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Tesla C1080
Memory needed
1.5 GB
Fastest
4,378 tok/s
GPT-2 (774M) reaches a parameter count of 774M. 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 Q8_0 and producing around 47.6 tokens per second.
At the other end sits B200, generating roughly 4,378 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Where it came from
GPT-2 (774M) was published by OpenAI, in the country recorded as United States of America, during February 2019. 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.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.
Understanding the speeds
Across every card that can run it, the middle of the range sits at 122.9 tokens per second. Exceeding reading speed outright: 809 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.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
What went into building it
Training it took a computation budget of roughly 5 × 10²¹ FLOP. 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 10,666,666,667 tokens of text.
It is tracked in the underlying dataset for one reason in particular: highly cited.
Step by step
How to choose a GPU for GPT-2 (774M)
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
The table lists every card able to hold GPT-2 (774M), needing around 1.5 GB at a compression of Q8_0. Capacity is the gate — a card either holds it or it does not.
-
02
Set the context length you will work at
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 GPT-2 (774M).
-
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
Sort by speed
Ranking by tokens per second follows memory bandwidth rather than core counts, for GPT-2 (774M). It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 4,378 tok/s.
-
05
Look at the headroom, not just the fit
The fit column separates cards that just manage it from those with room to spare, in the case of GPT-2 (774M). 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 GPT-2 (774M).
Answers
GPT-2 (774M) — common questions
GPT-2 (774M)— when was it released?
It was published in February 2019. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
GPT-2 (774M)— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language modeling/generation. 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.
GPT-2 (774M)— 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.
GPT-2 (774M)— how much compute was used to train it?
Training consumed around 5 × 10²¹ FLOP. 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.
GPT-2 (774M)— 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.
GPT-2 (774M)— 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.
GPT-2 (774M)— 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.
GPT-2 (774M)— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 2,627–7,004 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
GPT-2 (774M)— 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.5 GB, and produces roughly 47.6 tokens per second. The number of cards able to run it in total: 818.
GPT-2 (774M)— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 4,378 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.
GPT-2 (774M)— how much VRAM does it need?
It needs about 1.5 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.
GPT-2 (774M)— 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.5 GB and generating roughly 815 tokens per second. The fit is comfortable.
GPT-2 (774M)— 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.5 GB and generating roughly 499 tokens per second. The fit is comfortable.
GPT-2 (774M)— 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.5 GB and generating roughly 618 tokens per second. The fit is comfortable.
GPT-2 (774M)— 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.5 GB and generating roughly 733 tokens per second. The fit is comfortable.
GPT-2 (774M)— 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.
GPT-2 (774M)— how many parameters does it have?
It has a parameter count of 774M. Note that the initial paper release stated GPT-2 large had 762M parameters. The official github repo notes that this was due to an error: https://github.com/openai/gpt-2?tab=readme-ov-file. 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.
GPT-2 (774M)— who created it?
It was published by OpenAI, based in United States of America, an organisation categorised as industry.
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.