OPT-6.7B 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 K20c
5 GB · IQ4_XS · 27.4 tok/s
Fastest card
B200
506 tok/s · 180 GB
Which GPUs can run OPT-6.7B?
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.
589 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
506
tok/s
303–809 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 7.9 GB | Q8_0 | Comfortable |
|
506
tok/s
303–809 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 7.9 GB | Q8_0 | Comfortable |
|
404
tok/s
242–646 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 7.9 GB | Q8_0 | Comfortable |
|
404
tok/s
242–646 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 7.9 GB | Q8_0 | Comfortable |
|
323
tok/s
194–517 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 7.9 GB | Q8_0 | Comfortable |
|
309
tok/s
185–495 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 7.9 GB | Q8_0 | Comfortable |
|
309
tok/s
185–495 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 7.9 GB | Q8_0 | Comfortable |
|
296
tok/s
178–473 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 7.9 GB | Q8_0 | Comfortable |
|
263
tok/s
158–420 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 7.9 GB | Q8_0 | Comfortable |
|
263
tok/s
158–420 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 7.9 GB | Q8_0 | Comfortable |
|
263
tok/s
158–420 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 7.9 GB | Q8_0 | Comfortable |
|
249
tok/s
149–399 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 7.9 GB | Q8_0 | Comfortable |
|
212
tok/s
127–340 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 7.9 GB | Q8_0 | Comfortable |
|
212
tok/s
127–340 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 7.9 GB | Q8_0 | Comfortable |
|
212
tok/s
127–340 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 7.9 GB | Q8_0 | Comfortable |
|
212
tok/s
127–340 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 7.9 GB | Q8_0 | Comfortable |
|
212
tok/s
127–340 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 7.9 GB | Q8_0 | Comfortable |
|
162
tok/s
97–259 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 7.9 GB | Q8_0 | Comfortable |
|
162
tok/s
97–259 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 7.9 GB | Q8_0 | Comfortable |
|
137
tok/s
82–219 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 6.3 GB | Q6_K | Tight |
|
135
tok/s
81–216 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 7.9 GB | Q8_0 | Comfortable |
|
132
tok/s
79–211 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 7.9 GB | Q8_0 | Comfortable |
|
129
tok/s
77–206 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 7.9 GB | Q8_0 | Comfortable |
|
129
tok/s
77–206 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 7.9 GB | Q8_0 | Comfortable |
|
129
tok/s
77–206 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 7.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
- Meta AI
- Organisation type
- Industry
- Country
- United States of America
- Published
- 21 June 2022
- Authors
- Susan Zhang∗ , Stephen Roller∗ , Naman Goyal∗ , Mikel Artetxe, Moya Chen, Shuohui Chen, Christopher Dewan, Mona Diab, Xian Li, Xi Victoria Lin, Todor Mihaylov, Myle Ott† , Sam Shleifer† , Kurt Shuster, Daniel Simig, Punit Singh Koura, Anjali Sridhar, Tianlu Wang, Luke Zettlemoyer
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling, Chat, Language modeling/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
- 6.7B
- Training data
- 180,000,000,000 tokens
- Epochs
- 1.67
- Batch size
- 2,000,000
"How many instances are there in total (of each type, if appropriate)? The training data contains 180B tokens corresponding to 800 GB of data."
Table 1
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
- Comparison with other models
https://www.wolframalpha.com/input?i=6+FLOP+*+6.7+billion+*+300+billion 4.3e+23 (175B exact compute) * 6.7B/175B = 1.6462857e+22
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 (non-commercial)
- Training code
- Open source
non-commercial for weights: https://ai.meta.com/blog/democratizing-access-to-large-scale-language-models-with-opt-175b/ training code (MIT) https://github.com/facebookresearch/metaseq/blob/main/docs/training.md
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
- Citations
- 4,716
- Benchmark data
- OPT-6.7B
Sources
Where this record came from and when it was last checked.
- Reference
- OPT: Open Pre-trained Transformer Language Models
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run OPT-6.7B
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 506 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 506 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 404 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 404 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 323 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 309 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 309 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 296 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 263 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 263 tok/s
The smallest GPUs that still run OPT-6.7B
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Quadro P2200 5 GB · needs 4.4 GB · IQ4_XS · tight 26.4 tok/s
- 02 P102-100 5 GB · needs 4.4 GB · IQ4_XS · tight 58.1 tok/s
- 03 GeForce GTX 1060 5 GB 5 GB · needs 4.4 GB · IQ4_XS · tight 21.1 tok/s
- 04 Quadro P2000 5 GB · needs 4.4 GB · IQ4_XS · tight 18.5 tok/s
- 05 Tesla K20s 5 GB · needs 4.4 GB · IQ4_XS · tight 27.4 tok/s
- 06 Tesla K20m 5 GB · needs 4.4 GB · IQ4_XS · tight 27.4 tok/s
- 07 Tesla K20c 5 GB · needs 4.4 GB · IQ4_XS · tight 27.4 tok/s
- 08 RTX 1000 Mobile Ada Generation 6 GB · needs 4.8 GB · Q4_K_M · tight 28.0 tok/s
- 09 GeForce RTX 3050 6 GB 6 GB · needs 4.8 GB · Q4_K_M · tight 24.5 tok/s
- 10 Arc A380M 6 GB · needs 4.8 GB · Q4_K_M · tight 17.6 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla K20c
Memory needed
4.4 GB
Fastest
506 tok/s
OPT-6.7B reaches a parameter count of 6.7B. 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: 589.
The entry point is Tesla K20c, with a memory capacity of 5 GB, running it at a compression of IQ4_XS and producing around 27.4 tokens per second.
At the other end sits B200, generating roughly 506 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Background
OPT-6.7B was published by Meta AI, in the country recorded as United States of America, during June 2022. 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, Chat, Language modeling/generation, Question answering.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.
Reading the throughput figures
Across every card that can run it, the middle of the range sits at 27.3 tokens per second. Exceeding reading speed outright: 562 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
Producing it required arithmetic totalling around 1.2 × 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 180,000,000,000 tokens of text.
Step by step
How to choose a GPU for OPT-6.7B
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
Every card here has been checked against OPT-6.7B, needing around 4.4 GB at a compression of IQ4_XS. 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 OPT-6.7B.
-
03
Set a quality floor
The quantisation column varies by card, because a bigger card holds a more accurate copy, reaching a compression of IQ4_XS 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 OPT-6.7B. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 506 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 OPT-6.7B. 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
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 OPT-6.7B.
Answers
OPT-6.7B — common questions
OPT-6.7B— how much VRAM does it need?
It needs about 4.4 GB at a compression of IQ4_XS, 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.
OPT-6.7B— 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 Q6_K, using about 6.3 GB and generating roughly 137 tokens per second. The fit is tight.
OPT-6.7B— 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 7.9 GB and generating roughly 57.7 tokens per second. The fit is comfortable.
OPT-6.7B— 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 7.9 GB and generating roughly 71.4 tokens per second. The fit is comfortable.
OPT-6.7B— 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 7.9 GB and generating roughly 84.7 tokens per second. The fit is comfortable.
OPT-6.7B— 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.
OPT-6.7B— how many parameters does it have?
It has a parameter count of 6.7B. 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.
OPT-6.7B— who created it?
It was published by Meta AI, based in United States of America, an organisation categorised as industry.
OPT-6.7B— when was it released?
It was published in June 2022. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
OPT-6.7B— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language modeling, Chat, Language modeling/generation, Question answering. These are the areas it was designed around; they describe intent rather than a hard boundary.
OPT-6.7B— 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.
OPT-6.7B— how much compute was used to train it?
Training consumed around 1.2 × 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.
OPT-6.7B— 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. The nearest miss we calculate falls short by 1.2 GB. Every figure here assumes the whole model is resident on the card.
OPT-6.7B— would two GPUs run it faster?
Capacity adds across cards; throughput does not. The number of cards already holding it on their own: 589. So a second card is rarely the answer here.
OPT-6.7B— 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: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
OPT-6.7B— how accurate are these speed estimates?
They are calculated from specifications rather than measured, and each carries a range. One example: 303–809 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
OPT-6.7B— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Tesla K20c, with a memory capacity of 5 GB. It runs the model at a compression of IQ4_XS using about 4.4 GB, and produces roughly 27.4 tokens per second. The number of cards able to run it in total: 589.
OPT-6.7B— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 506 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: 562.
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.