ProtT5-XL-U50 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 · Q6_K · 17.9 tok/s
Fastest card
B200
1,129 tok/s · 180 GB
Which GPUs can run ProtT5-XL-U50?
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 | |||||
|---|---|---|---|---|---|---|---|
|
1,129
tok/s
678–1,807 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 3.9 GB | Q8_0 | Comfortable |
|
1,129
tok/s
678–1,807 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 3.9 GB | Q8_0 | Comfortable |
|
902
tok/s
541–1,443 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 3.9 GB | Q8_0 | Comfortable |
|
902
tok/s
541–1,443 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 3.9 GB | Q8_0 | Comfortable |
|
721
tok/s
433–1,154 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 3.9 GB | Q8_0 | Comfortable |
|
690
tok/s
414–1,105 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 3.9 GB | Q8_0 | Comfortable |
|
690
tok/s
414–1,105 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 3.9 GB | Q8_0 | Comfortable |
|
661
tok/s
396–1,057 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 3.9 GB | Q8_0 | Comfortable |
|
586
tok/s
352–938 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 3.9 GB | Q8_0 | Comfortable |
|
586
tok/s
352–938 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 3.9 GB | Q8_0 | Comfortable |
|
586
tok/s
352–938 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 3.9 GB | Q8_0 | Comfortable |
|
556
tok/s
334–890 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
474
tok/s
285–759 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
474
tok/s
285–759 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 3.9 GB | Q8_0 | Comfortable |
|
474
tok/s
285–759 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
474
tok/s
285–759 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
474
tok/s
285–759 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 3.9 GB | Q8_0 | Comfortable |
|
361
tok/s
217–578 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 3.9 GB | Q8_0 | Comfortable |
|
361
tok/s
217–578 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 3.9 GB | Q8_0 | Comfortable |
|
301
tok/s
181–482 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 3.9 GB | Q8_0 | Comfortable |
|
295
tok/s
177–471 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 3.9 GB | Q8_0 | Comfortable |
|
288
tok/s
173–461 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 3.9 GB | Q8_0 | Comfortable |
|
288
tok/s
173–461 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 3.9 GB | Q8_0 | Comfortable |
|
288
tok/s
173–461 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 3.9 GB | Q8_0 | Comfortable |
|
288
tok/s
173–461 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 3.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
- Technical University of Munich,Med AI Technology,NVIDIA,Oak Ridge National Laboratory,Google,Seoul National University
- Organisation type
- Academia,Industry,Government,Industry,Academia
- Country
- Germany, China, United States of America, Korea (Republic of)
- Published
- 4 May 2021
- Authors
- Ahmed Elnaggar, Michael Heinzinger, Christian Dallago, Ghalia Rehawi, Yu Wang, Llion Jones, Tom Gibbs, Tamas Feher, Christoph Angerer, Martin Steinegger, Debsindhu Bhowmik, Burkhard Rost
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Biology
- Task
- Proteins, Protein or nucleotide language model (pLM/nLM), Protein contact and distance prediction
- Numerical format
- FP32
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
- 3B
- Training data
- 19,582,371,375 tokens
Table 2
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.9 × 10²² FLOP
- How it was established
- Operation counting
991K steps, 2048 batch, 512 sequence length (Table 2) Total tokens: 991K*2048*512=1039138816000 FLOP: 6*1039138816000*3000000000=18704498688000000000000
The training run
What it physically took to train: which chips, how many, for how long, and what that drew from the wall.
- Chips used
- 256
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
- Unreleased
- Hugging Face
- Rostlab
Academic Free License v3.0 License https://huggingface.co/Rostlab/prot_t5_xl_uniref50 It seems that there is no training code here, only inference and fine-tuning https://github.com/agemagician/ProtTrans
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,SOTA improvement
- Record confidence
- Confident
Table 3 "For the per-residue predictions the transfer of the most informative embeddings (ProtT5) for the first time outperformed the state-of-the-art without using evolutionary information" SOTA performance on New364 (new test set introduced in this paper)
Sources
Where this record came from and when it was last checked.
- Reference
- ProtTrans: Towards Cracking the Language of Life’s Code Through Self-Supervised Learning
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run ProtT5-XL-U50
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 1,129 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 1,129 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 902 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 902 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 721 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 690 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 690 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 661 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 586 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 586 tok/s
The smallest GPUs that still run ProtT5-XL-U50
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 3.2 GB · Q6_K · tight 19.7 tok/s
- 02 RTX A400 4 GB · needs 3.2 GB · Q6_K · tight 19.7 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 3.2 GB · Q6_K · tight 26.3 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 3.2 GB · Q6_K · tight 39.4 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 3.2 GB · Q6_K · tight 7.0 tok/s
- 06 Radeon RX 6450M 4 GB · needs 3.2 GB · Q6_K · tight 20.5 tok/s
- 07 Radeon RX 6550M 4 GB · needs 3.2 GB · Q6_K · tight 23.0 tok/s
- 08 Radeon RX 6550S 4 GB · needs 3.2 GB · Q6_K · tight 20.5 tok/s
- 09 Arc A310 4 GB · needs 3.2 GB · Q6_K · tight 16.5 tok/s
- 10 Arc Pro A30M 4 GB · needs 3.2 GB · Q6_K · tight 17.1 tok/s
What the numbers mean
What it takes to run this model
Minimum card
Tesla C1080
Memory needed
3.2 GB
Fastest
1,129 tok/s
ProtT5-XL-U50 is small enough at 3B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.
The smallest card that holds it is the Tesla C1080 with 4 GB, running it at Q6_K and producing around 17.9 tokens per second.
A B200 is the fastest we calculate for it: about 1,129 tokens per second, from 8,000 GB/s of memory bandwidth.
Where it came from
ProtT5-XL-U50 was published by Technical University of Munich,Med AI Technology,NVIDIA,Oak Ridge National Laboratory,Google,Seoul National University, in Germany, in May 2021. The organisation is categorised as academia,Industry,Government,Industry,Academia.
It works in Biology, and is recorded as doing proteins, Protein or nucleotide language model (pLM/nLM), Protein contact and distance prediction.
Published weights mean the model runs on your machine rather than someone else's, which is what makes the hardware question below answerable at all. It is published under the Rostlab organisation on Hugging Face.
Understanding the speeds
The median result is around 35.8 tokens per second; 780 cards produce text faster than most people read it.
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.
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
Producing it required around 1.9 × 10²² FLOP of arithmetic, which is a statement about the training budget rather than about inference.
It was trained on about 19,582,371,375 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 ProtT5-XL-U50
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 ProtT5-XL-U50 actually needs — around 3.2 GB at Q6_K. No amount of processing power compensates for a card that cannot hold it.
-
02
Match the context to your actual use
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason ProtT5-XL-U50 stops fitting a card that seemed fine.
-
03
Choose how far you will compress it
Compression is what makes ProtT5-XL-U50 fit smaller cards, at some cost in accuracy — Q6_K 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 ProtT5-XL-U50. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 1,129 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage ProtT5-XL-U50 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 ProtT5-XL-U50 is settled.
Answers
ProtT5-XL-U50 — common questions
When was ProtT5-XL-U50 released?
ProtT5-XL-U50 was published in May 2021. 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 ProtT5-XL-U50 used for?
ProtT5-XL-U50 works in Biology, and is recorded as handling proteins, Protein or nucleotide language model (pLM/nLM), Protein contact and distance prediction. 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.
Where can I download ProtT5-XL-U50?
Its weights are published under the Rostlab organisation on Hugging Face. We do not host model files — this site calculates what hardware is needed to run them.
How much compute was used to train ProtT5-XL-U50?
Around 1.9 × 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.
Can I run ProtT5-XL-U50 if it does not fit in my GPU?
It can be split between the card and system memory, but ProtT5-XL-U50 generates painfully slowly that way. Nothing on this page assumes offloading.
Would two GPUs run ProtT5-XL-U50 faster?
Two cards buy memory rather than speed. That matters for ProtT5-XL-U50 only if one card cannot hold it — 818 can, so a second adds little.
Why does the quantisation differ between cards for ProtT5-XL-U50?
Each card is shown running the least-compressed copy it can hold, and ProtT5-XL-U50 appears at 2 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these ProtT5-XL-U50 speed estimates?
They are calculated from specifications rather than measured, and each carries a range — 678–1,807 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
What GPU do I need to run ProtT5-XL-U50?
The smallest card in our catalogue that holds ProtT5-XL-U50 is the Tesla C1080, with 4 GB of memory. It runs the model at Q6_K using about 3.2 GB, and produces roughly 17.9 tokens per second. 818 cards in total can run it.
How fast is ProtT5-XL-U50 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 1,129 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 780 of the cards that can run ProtT5-XL-U50 clear that.
How much VRAM does ProtT5-XL-U50 need?
About 3.2 GB at Q6_K 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 ProtT5-XL-U50 on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 3.9 GB and generating roughly 210 tokens per second — a comfortable fit.
Can I run ProtT5-XL-U50 on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 3.9 GB and generating roughly 129 tokens per second — a comfortable fit.
Can I run ProtT5-XL-U50 on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 3.9 GB and generating roughly 160 tokens per second — a comfortable fit.
Can I run ProtT5-XL-U50 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 3.9 GB and generating roughly 189 tokens per second — a comfortable fit.
Is ProtT5-XL-U50 open source?
Its weights are published, so ProtT5-XL-U50 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 ProtT5-XL-U50 have?
ProtT5-XL-U50 has 3B parameters. Table 2. 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.
Who created ProtT5-XL-U50?
ProtT5-XL-U50 was published by Technical University of Munich,Med AI Technology,NVIDIA,Oak Ridge National Laboratory,Google,Seoul National University, based in Germany, categorised as academia,Industry,Government,Industry,Academia.
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.