RoBERTa Large TPS calculator

Open weights Facebook,University of Washington 355M parameters July 2019

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 that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla C1080

4 GB · Q8_0 · 104 tok/s

Fastest card

B200

9,544 tok/s · 180 GB

Which GPUs can run RoBERTa 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
9,544 tok/s

5,727–15,271 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 1.1 GB Q8_0 Comfortable
9,544 tok/s

5,727–15,271 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 1.1 GB Q8_0 Comfortable
7,621 tok/s

4,573–12,194 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 1.1 GB Q8_0 Comfortable
7,621 tok/s

4,573–12,194 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 1.1 GB Q8_0 Comfortable
6,095 tok/s

3,657–9,752 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 1.1 GB Q8_0 Comfortable
5,834 tok/s

3,500–9,334 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 1.1 GB Q8_0 Comfortable
5,834 tok/s

3,500–9,334 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 1.1 GB Q8_0 Comfortable
5,583 tok/s

3,350–8,933 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 1.1 GB Q8_0 Comfortable
4,955 tok/s

2,973–7,928 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 1.1 GB Q8_0 Comfortable
4,955 tok/s

2,973–7,928 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 1.1 GB Q8_0 Comfortable
4,955 tok/s

2,973–7,928 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 1.1 GB Q8_0 Comfortable
4,701 tok/s

2,820–7,521 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 1.1 GB Q8_0 Comfortable
4,009 tok/s

2,405–6,414 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.1 GB Q8_0 Comfortable
4,009 tok/s

2,405–6,414 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 1.1 GB Q8_0 Comfortable
4,009 tok/s

2,405–6,414 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 1.1 GB Q8_0 Comfortable
4,009 tok/s

2,405–6,414 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.1 GB Q8_0 Comfortable
4,009 tok/s

2,405–6,414 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 1.1 GB Q8_0 Comfortable
3,052 tok/s

1,831–4,884 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 1.1 GB Q8_0 Comfortable
3,052 tok/s

1,831–4,884 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 1.1 GB Q8_0 Comfortable
2,544 tok/s

1,526–4,070 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 1.1 GB Q8_0 Comfortable
2,489 tok/s

1,494–3,983 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 1.1 GB Q8_0 Comfortable
2,434 tok/s

1,460–3,894 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 1.1 GB Q8_0 Comfortable
2,434 tok/s

1,460–3,894 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 1.1 GB Q8_0 Comfortable
2,434 tok/s

1,460–3,894 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 1.1 GB Q8_0 Comfortable
2,434 tok/s

1,460–3,894 · 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,University of Washington
Organisation type
Industry,Academia
Country
United States of America
Published
1 July 2019
Authors
Yinhan Liu, Myle Ott, Naman Goyal, Jingfei Du, Mandar Joshi, Danqi Chen, Omer Levy, Mike Lewis, Luke Zettlemoyer, Veselin Stoyanov

What it does

The problem areas the model was built for. A model can carry several of each.

Domain
Language
Task
Question answering, Language modeling/generation
Numerical format
FP16

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
355M

355M https://github.com/facebookresearch/fairseq/blob/main/examples/roberta/README.md

Training data
42,666,666,666 tokens

160GB*200M words/GB * (4 tokens / 3 words) = 3.2e10 tokens max steps 500k batch size 8k "We pretrain with sequences of at most T = 512 tokens." 500000*8000*512 = 2.048e+12 tokens

Epochs
48

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
8.5 × 10²¹ FLOP

Section 5: We pretrain our model using 1024 V100 GPUs for approximately one day. Note this is the base pretraining comparable to BERT, 100k steps. Subsequently they do more: "increasing the number of pretraining steps from 100K to 300K, and then further to 500K". So assume 5x the 1024 V100 GPUs for 1d estimate. Mixed precision tensor cores get 1.25e14 FLOP/s. 1024 * 1.25e14 * 5 * 24 * 3600 * 0.3 = 1.65888e22 6ND estimate: batches are 8k sequences of 512 tokens; 500k updates means the model s…

How it was established
Hardware,Operation counting,Third-party estimation

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 Tesla V100 DGXS 32 GB
Chips used
1,024
Chip-hours
122,880
Wall-clock time
120 hours

First the model is pretrained for 100k steps on 1024 GPUs for 1 day, then pretraining is increased to 500k steps, so assuming they used the same number of GPUs, this would have taken 5 days.

Power draw
526.2 kW
Compute cost
$85,350

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

code and weights: https://github.com/facebookresearch/fairseq/blob/main/examples/roberta/README.md pretrain code: https://github.com/facebookresearch/fairseq/blob/main/examples/roberta/README.pretraining.md repo is MIT license

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,SOTA improvement

"Our best model achieves state-of-the-art results on GLUE, RACE and SQuAD"

Record confidence
Confident
Citations
29,641

Sources

Where this record came from and when it was last checked.

Reference
RoBERTa: A Robustly Optimized BERT Pretraining Approach
Last updated
25 May 2026

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

Tesla C1080

Memory needed

1.1 GB

Fastest

9,544 tok/s

RoBERTa Large reaches a parameter count of 355M. 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 entry point is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 104 tokens per second.

The quickest result comes from B200, generating roughly 9,544 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

About this model

RoBERTa Large was published by Facebook,University of Washington, in the country recorded as United States of America, during July 2019. The publishing organisation is categorised as industry,Academia.

It works in the domain of Language, and is recorded as performing the task of question answering, Language modeling/generation.

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 268.0 tokens per second. Producing text faster than most people read it: 817 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.

How it was trained

The training run consumed about 8.5 × 10²¹ FLOP, on hardware recorded as NVIDIA Tesla V100 DGXS 32 GB. That figure measures what producing the model cost, and has no bearing on how fast it answers.

Training consumed a corpus of around 42,666,666,666 tokens of text.

It is tracked in the underlying dataset for one reason in particular: highly cited,SOTA improvement.

Step by step

How to choose a GPU for RoBERTa Large

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Read the memory figure first

    The table lists every card able to hold RoBERTa Large, needing around 1.1 GB at a compression of Q8_0. Capacity is the gate — a card either holds it or it does not.

  2. 02

    Decide how long your conversations run

    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 RoBERTa Large.

  3. 03

    Set a quality floor

    The quantisation column varies by card, because a bigger card holds a more accurate copy, 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.

  4. 04

    Compare tokens per second, not specifications

    The speed ordering is effectively an ordering by memory bandwidth, for RoBERTa Large. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 9,544 tok/s.

  5. 05

    Read the fit column last

    A tight fit runs, but leaves nothing spare for a longer conversation, in the case of RoBERTa 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.

  6. 06

    Check the card from the other side

    Following a card through to its own page shows every other model it can hold, which is the question that follows once you have settled on RoBERTa Large.

Answers

RoBERTa Large — common questions

01

RoBERTa Large— how many parameters does it have?

It has a parameter count of 355M. 355M https://github.com/facebookresearch/fairseq/blob/main/examples/roberta/README.md. 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.

02

RoBERTa Large— who created it?

It was published by Facebook,University of Washington, based in United States of America, an organisation categorised as industry,Academia.

03

RoBERTa Large— when was it released?

It was published in July 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.

04

RoBERTa Large— what is it used for?

It works in the domain of Language, and is recorded as handling the task of question answering, Language modeling/generation. These are the areas it was designed around; they describe intent rather than a hard boundary.

05

RoBERTa 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.

06

RoBERTa Large— how much compute was used to train it?

Training consumed around 8.5 × 10²¹ FLOP, on hardware recorded as NVIDIA Tesla V100 DGXS 32 GB. 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.

07

RoBERTa Large— 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.

08

RoBERTa Large— 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.

09

RoBERTa 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.

10

RoBERTa 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,727–15,271 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

11

RoBERTa 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 104 tokens per second. The number of cards able to run it in total: 818.

12

RoBERTa Large— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 9,544 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.

13

RoBERTa 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.

14

RoBERTa 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,778 tokens per second. The fit is comfortable.

15

RoBERTa 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 1,089 tokens per second. The fit is comfortable.

16

RoBERTa 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,348 tokens per second. The fit is comfortable.

17

RoBERTa 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,599 tokens per second. The fit is comfortable.

18

RoBERTa 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.

Source

Original publication

Record last updated 25 May 2026

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.