XLM-RoBERTa 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 · 67.0 tok/s
Fastest card
B200
6,160 tok/s · 180 GB
Which GPUs can run XLM-RoBERTa?
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 | |||||
|---|---|---|---|---|---|---|---|
|
6,160
tok/s
3,696–9,857 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.3 GB | Q8_0 | Comfortable |
|
6,160
tok/s
3,696–9,857 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.3 GB | Q8_0 | Comfortable |
|
4,919
tok/s
2,952–7,871 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.3 GB | Q8_0 | Comfortable |
|
4,919
tok/s
2,952–7,871 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.3 GB | Q8_0 | Comfortable |
|
3,934
tok/s
2,361–6,295 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.3 GB | Q8_0 | Comfortable |
|
3,766
tok/s
2,259–6,025 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.3 GB | Q8_0 | Comfortable |
|
3,766
tok/s
2,259–6,025 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.3 GB | Q8_0 | Comfortable |
|
3,604
tok/s
2,162–5,766 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.3 GB | Q8_0 | Comfortable |
|
3,198
tok/s
1,919–5,117 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.3 GB | Q8_0 | Comfortable |
|
3,198
tok/s
1,919–5,117 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.3 GB | Q8_0 | Comfortable |
|
3,198
tok/s
1,919–5,117 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.3 GB | Q8_0 | Comfortable |
|
3,034
tok/s
1,820–4,854 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,587
tok/s
1,552–4,140 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,587
tok/s
1,552–4,140 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.3 GB | Q8_0 | Comfortable |
|
2,587
tok/s
1,552–4,140 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,587
tok/s
1,552–4,140 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
2,587
tok/s
1,552–4,140 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.3 GB | Q8_0 | Comfortable |
|
1,970
tok/s
1,182–3,152 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.3 GB | Q8_0 | Comfortable |
|
1,970
tok/s
1,182–3,152 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.3 GB | Q8_0 | Comfortable |
|
1,642
tok/s
985–2,627 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.3 GB | Q8_0 | Comfortable |
|
1,607
tok/s
964–2,571 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.3 GB | Q8_0 | Comfortable |
|
1,571
tok/s
943–2,513 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.3 GB | Q8_0 | Comfortable |
|
1,571
tok/s
943–2,513 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.3 GB | Q8_0 | Comfortable |
|
1,571
tok/s
943–2,513 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.3 GB | Q8_0 | Comfortable |
|
1,571
tok/s
943–2,513 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.3 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
- 5 November 2019
- Authors
- Alexis Conneau, Kartikay Khandelwal, Naman Goyal, Vishrav Chaudhary, Guillaume Wenzek, Francisco Guzmán, Edouard Grave, Myle Ott, 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
- Named entity recognition (NER), Question answering, Text classification
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
- 550M
- Training data
- 167,000,000,000 tokens
The number of parameters in the model is specified as "550M params" for XLM-R.
size of CC100 - copied from other rows
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
- 2.1 × 10²² FLOP
- How it was established
- Operation counting
"We use the multilingual MLM loss and train our XLM-R model for 1.5 Million updates on five-hundred 32GB Nvidia V100 GPUs with a batch size of 8192. " 6ND: Sequence length was probably 512, based on follow up paper (XLM-R XXL) 6 * 550e6 * 1.5e6 * 8192 * 512 = 2.076e22
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
- 500
- Power draw
- 256.2 kW
- Compute cost
- $77,861
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 (non-commercial)
non-commercial: https://github.com/facebookresearch/XLM?tab=License-1-ov-file#readme data is wikipedia
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
- Record confidence
- Confident
- Citations
- 8,373
citation "which obtains state-of-the-art performance on cross-lingual classification, sequence labeling and question answering"
Sources
Where this record came from and when it was last checked.
- Reference
- Unsupervised Cross-lingual Representation Learning at Scale
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run XLM-RoBERTa
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 6,160 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 6,160 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 4,919 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 4,919 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 3,934 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 3,766 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 3,766 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 3,604 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 3,198 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 3,198 tok/s
The smallest GPUs that still run XLM-RoBERTa
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.3 GB · Q8_0 · comfortable 73.9 tok/s
- 02 RTX A400 4 GB · needs 1.3 GB · Q8_0 · comfortable 73.9 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.3 GB · Q8_0 · comfortable 98.6 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.3 GB · Q8_0 · comfortable 148 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.3 GB · Q8_0 · comfortable 26.3 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.3 GB · Q8_0 · comfortable 76.9 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.3 GB · Q8_0 · comfortable 86.5 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.3 GB · Q8_0 · comfortable 76.9 tok/s
- 09 Arc A310 4 GB · needs 1.3 GB · Q8_0 · comfortable 62.1 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.3 GB · Q8_0 · comfortable 64.1 tok/s
What the numbers mean
What you need to run it
Minimum card
Tesla C1080
Memory needed
1.3 GB
Fastest
6,160 tok/s
XLM-RoBERTa is small enough at 550M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The least hardware that works is a Tesla C1080. Its 4 GB is enough at Q8_0 compression, giving roughly 67.0 tokens per second.
The quickest result comes from a B200 at around 6,160 tokens per second — its 8,000 GB/s of bandwidth is what buys that.
Background
XLM-RoBERTa was published by Facebook AI, in United States of America, in November 2019. The organisation is categorised as industry.
It works in Language, and is recorded as doing named entity recognition (NER), Question answering, Text classification.
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.
Reading the throughput figures
Half the cards that hold it manage more than 173.0 tokens per second, and 809 exceed reading speed outright.
It is a dense model, so every parameter is read for every token produced. That makes speed track memory bandwidth almost exactly — a card with twice the bandwidth generates roughly twice as fast.
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.
What went into building it
Producing it required around 2.1 × 10²² FLOP of arithmetic, on NVIDIA Tesla V100 DGXS 32 GB, which is a statement about the training budget rather than about inference.
Around 167,000,000,000 tokens went into training it.
The reason it appears in this catalogue at all is highly cited,SOTA improvement.
Step by step
How to choose a GPU for XLM-RoBERTa
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
Look at what XLM-RoBERTa actually needs — around 1.3 GB at Q8_0. No amount of processing power compensates for a card that cannot hold it.
-
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: at long context XLM-RoBERTa can slip off a card that handles short questions easily.
-
03
Set a quality floor
Compression is what makes XLM-RoBERTa fit smaller cards, at some cost in accuracy — Q8_0 on the smallest card that fits. A minimum quality removes the ones that go too far.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for XLM-RoBERTa. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 6,160 tok/s.
-
05
Look at the headroom, not just the fit
The fit column separates cards that just manage XLM-RoBERTa from those with room to spare. Buy for the second if the context might grow.
-
06
Open the card you have settled on
Following a card through to its own page shows every other model it can hold, which is the question that follows once XLM-RoBERTa is settled.
Answers
XLM-RoBERTa — common questions
Who created XLM-RoBERTa?
XLM-RoBERTa was published by Facebook AI, based in United States of America, categorised as industry.
When was XLM-RoBERTa released?
XLM-RoBERTa was published in November 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.
What is XLM-RoBERTa used for?
XLM-RoBERTa works in Language, and is recorded as handling named entity recognition (NER), Question answering, Text classification. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download XLM-RoBERTa?
The weights for XLM-RoBERTa are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train XLM-RoBERTa?
Around 2.1 × 10²² FLOP, on 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.
Can I run XLM-RoBERTa if it does not fit in my GPU?
It can be split between the card and system memory, but XLM-RoBERTa generates painfully slowly that way. Nothing on this page assumes offloading.
Would two GPUs run XLM-RoBERTa faster?
Two cards buy memory rather than speed. That matters for XLM-RoBERTa only if one card cannot hold it — 818 can, so a second adds little.
Why does the quantisation differ between cards for XLM-RoBERTa?
Each card is shown running the least-compressed copy it can hold, and XLM-RoBERTa appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these XLM-RoBERTa speed estimates?
These are estimates with real error bars. The fastest result here, 3,696–9,857 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.
What GPU do I need to run XLM-RoBERTa?
The smallest card in our catalogue that holds XLM-RoBERTa is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.3 GB, and produces roughly 67.0 tokens per second. 818 cards in total can run it.
How fast is XLM-RoBERTa on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 6,160 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 809 of the cards that can run XLM-RoBERTa clear that.
How much VRAM does XLM-RoBERTa need?
About 1.3 GB at Q8_0 compression, 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.
Can I run XLM-RoBERTa on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.3 GB and generating roughly 1,147 tokens per second — a comfortable fit.
Can I run XLM-RoBERTa on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.3 GB and generating roughly 703 tokens per second — a comfortable fit.
Can I run XLM-RoBERTa on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.3 GB and generating roughly 870 tokens per second — a comfortable fit.
Can I run XLM-RoBERTa on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.3 GB and generating roughly 1,032 tokens per second — a comfortable fit.
Is XLM-RoBERTa open source?
Its weights are published, so XLM-RoBERTa 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.
How many parameters does XLM-RoBERTa have?
XLM-RoBERTa has 550M parameters. The number of parameters in the model is specified as "550M params" for XLM-R. 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.
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.