BART-large 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 · 90.7 tok/s
Fastest card
B200
8,339 tok/s · 180 GB
Which GPUs can run BART-large?
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 | |||||
|---|---|---|---|---|---|---|---|
|
8,339
tok/s
5,004–13,343 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.1 GB | Q8_0 | Comfortable |
|
8,339
tok/s
5,004–13,343 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.1 GB | Q8_0 | Comfortable |
|
6,659
tok/s
3,996–10,655 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
6,659
tok/s
3,996–10,655 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.1 GB | Q8_0 | Comfortable |
|
5,326
tok/s
3,195–8,521 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
5,097
tok/s
3,058–8,156 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
5,097
tok/s
3,058–8,156 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.1 GB | Q8_0 | Comfortable |
|
4,879
tok/s
2,927–7,806 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.1 GB | Q8_0 | Comfortable |
|
4,330
tok/s
2,598–6,928 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,330
tok/s
2,598–6,928 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,330
tok/s
2,598–6,928 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.1 GB | Q8_0 | Comfortable |
|
4,107
tok/s
2,464–6,571 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,503
tok/s
2,102–5,604 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,503
tok/s
2,102–5,604 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.1 GB | Q8_0 | Comfortable |
|
3,503
tok/s
2,102–5,604 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,503
tok/s
2,102–5,604 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
3,503
tok/s
2,102–5,604 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,667
tok/s
1,600–4,267 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,667
tok/s
1,600–4,267 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,222
tok/s
1,333–3,556 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,175
tok/s
1,305–3,480 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.1 GB | Q8_0 | Comfortable |
|
2,127
tok/s
1,276–3,402 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.1 GB | Q8_0 | Comfortable |
|
2,127
tok/s
1,276–3,402 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.1 GB | Q8_0 | Comfortable |
|
2,127
tok/s
1,276–3,402 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.1 GB | Q8_0 | Comfortable |
|
2,127
tok/s
1,276–3,402 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.1 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
- Facebook AI
- Organisation type
- Industry
- Country
- United States of America
- Published
- 29 October 2019
- Authors
- Mike Lewis, Yinhan Liu, Naman Goyal, Marjan Ghazvininejad, Abdelrahman Mohamed, Omer Levy, Ves Stoyanov, 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/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
- 406.3M
- Training data
- 42,666,666,666 tokens
"In total, BART contains roughly 10% more parameters than the equivalently sized BERT model." I counted the parameters in the huggingface model https://huggingface.co/facebook/bart-large/tree/main from transformers import AutoTokenizer, AutoModel tokenizer = AutoTokenizer.from_pretrained("facebook/bart-large") model = AutoModel.from_pretrained("facebook/bart-large") sum(p.numel() for p in model.parameters() if p.requires_grad)
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
Models: https://github.com/facebookresearch/fairseq/blob/main/examples/bart/README.md MIT license: https://github.com/facebookresearch/fairseq/blob/main/LICENSE
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
- Likely
- Citations
- 12,770
Sources
Where this record came from and when it was last checked.
- Reference
- BART: Denoising Sequence-to-Sequence Pre-training for Natural Language Generation, Translation, and Comprehension
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run BART-large
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 8,339 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 8,339 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 6,659 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 6,659 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 5,326 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 5,097 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 5,097 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 4,879 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 4,330 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 4,330 tok/s
The smallest GPUs that still run BART-large
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.1 GB · Q8_0 · comfortable 100 tok/s
- 02 RTX A400 4 GB · needs 1.1 GB · Q8_0 · comfortable 100 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.1 GB · Q8_0 · comfortable 133 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.1 GB · Q8_0 · comfortable 200 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.1 GB · Q8_0 · comfortable 35.6 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.1 GB · Q8_0 · comfortable 104 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.1 GB · Q8_0 · comfortable 117 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.1 GB · Q8_0 · comfortable 104 tok/s
- 09 Arc A310 4 GB · needs 1.1 GB · Q8_0 · comfortable 84.0 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.1 GB · Q8_0 · comfortable 86.7 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla C1080
Memory needed
1.1 GB
Fastest
8,339 tok/s
BART-large reaches a parameter count of 406.3M. 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 90.7 tokens per second.
The quickest result comes from B200, generating roughly 8,339 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
BART-large was published by Facebook AI, in the country recorded as United States of America, during October 2019. 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/generation, Question answering.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.
How fast it runs, and why
Half the cards that hold it manage more than 234.2 tokens per second. Producing text faster than most people read it: 817 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.
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.
Training and provenance
It was trained on a corpus of about 42,666,666,666 tokens of text.
Its inclusion criterion: highly cited.
Step by step
How to choose a GPU for BART-large
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 BART-large, needing around 1.1 GB at a compression of Q8_0. That figure, not the headline performance of a card, is what decides whether it runs.
-
02
Decide how long your conversations run
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 BART-large.
-
03
Choose how far you will compress it
Compression is what makes a model fit smaller cards, at some cost in accuracy, 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
The speed ordering is effectively an ordering by memory bandwidth, for BART-large. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 8,339 tok/s.
-
05
Read the fit column last
Tight means it loads and works with no room to raise the context later, in the case of BART-large. 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 BART-large.
Answers
BART-large — common questions
BART-large— 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.1 GB and generating roughly 1,553 tokens per second. The fit is comfortable.
BART-large— 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.1 GB and generating roughly 951 tokens per second. The fit is comfortable.
BART-large— 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.1 GB and generating roughly 1,178 tokens per second. The fit is comfortable.
BART-large— 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.1 GB and generating roughly 1,397 tokens per second. The fit is comfortable.
BART-large— 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.
BART-large— how many parameters does it have?
It has a parameter count of 406.3M. "In total, BART contains roughly 10% more parameters than the equivalently sized BERT model." I counted the parameters in the huggingface model https://huggingface.co/facebook/bart-large/tree/main from transformers import AutoTokenizer, AutoModel tokenizer = AutoTokenizer.from_pretrained("facebook/bart-large") model = AutoModel.from_pretrained("facebook/bart-large") sum(p.numel() for p in model.parameters() if p.requires_grad). 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.
BART-large— who created it?
It was published by Facebook AI, based in United States of America, an organisation categorised as industry.
BART-large— when was it released?
It was published in October 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.
BART-large— what is it used for?
It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Question answering. These are the areas it was designed around; they describe intent rather than a hard boundary.
BART-large— 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.
BART-large— 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. Every figure here assumes the whole model is resident on the card.
BART-large— would two GPUs run it faster?
A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 818. So a second card is rarely the answer here.
BART-large— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
BART-large— how accurate are these speed estimates?
These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 5,004–13,343 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
BART-large— 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.1 GB, and produces roughly 90.7 tokens per second. The number of cards able to run it in total: 818.
BART-large— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 8,339 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: 817.
BART-large— how much VRAM does it need?
It needs about 1.1 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.
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.