UDSMProt TPS calculator

Open weights Fraunhofer Heinrich Hertz Institute 28.3M parameters September 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 · 1,302 tok/s

Fastest card

B200

119,710 tok/s · 180 GB

Which GPUs can run UDSMProt?

Set the inputs, read the answer

Context length tokens

A longer conversation needs more memory, which can push this model off smaller cards.

Minimum quality

Hides cards that would only fit the model by compressing it below this point.

Search cards

Card memory

Also show cards that cannot run it

818 cards match

Calculating

					Needs	Quantisation	Fit
119,710 tok/s 71,826–191,535 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	0.7 GB	Q8_0	Comfortable
119,710 tok/s 71,826–191,535 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	0.7 GB	Q8_0	Comfortable
95,591 tok/s 57,355–152,946 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	0.7 GB	Q8_0	Comfortable
95,591 tok/s 57,355–152,946 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	0.7 GB	Q8_0	Comfortable
76,450 tok/s 45,870–122,319 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
73,172 tok/s 43,903–117,076 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	0.7 GB	Q8_0	Comfortable
73,172 tok/s 43,903–117,076 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	0.7 GB	Q8_0	Comfortable
70,030 tok/s 42,018–112,048 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	0.7 GB	Q8_0	Comfortable
62,152 tok/s 37,291–99,443 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
62,152 tok/s 37,291–99,443 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
62,152 tok/s 37,291–99,443 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
58,957 tok/s 35,374–94,331 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
50,278 tok/s 30,167–80,445 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
50,278 tok/s 30,167–80,445 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	0.7 GB	Q8_0	Comfortable
50,278 tok/s 30,167–80,445 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
50,278 tok/s 30,167–80,445 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
50,278 tok/s 30,167–80,445 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
38,283 tok/s 22,970–61,253 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	0.7 GB	Q8_0	Comfortable
38,283 tok/s 22,970–61,253 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	0.7 GB	Q8_0	Comfortable
31,903 tok/s 19,142–51,044 · low confidence	Data Center GPU Max 1550 Intel	128 GB	3,280 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
31,222 tok/s 18,733–49,955 · low confidence	Data Center GPU Max Subsystem Intel	128 GB	3,210 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
30,526 tok/s 18,316–48,842 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	0.7 GB	Q8_0	Comfortable
30,526 tok/s 18,316–48,842 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	0.7 GB	Q8_0	Comfortable
30,526 tok/s 18,316–48,842 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	0.7 GB	Q8_0	Comfortable
30,526 tok/s 18,316–48,842 · low confidence	H100 CNX NVIDIA	80 GB	2,040 GB/s	Mar 2023	0.7 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: Fraunhofer Heinrich Hertz Institute
Organisation type: Research collective
Country: Germany
Published: 4 September 2019
Authors: Nils Strodthoff, Patrick Wagner, Markus Wenzel, and Wojciech Samek

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), Enzyme function prediction
Approach: Self-supervised learning

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: 28.3M
Training data: 149,700,000 tokens
Epochs: 30

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: 6.4 × 10¹⁷ FLOP
How it was established: Operation counting

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

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: SOTA improvement
Record confidence: Likely

Sources

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

Reference: UDSMProt: Universal Deep Sequence Models for Protein Classification
Last updated: 28 November 2025

The extremes

The ten fastest GPUs that run UDSMProt

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.

The smallest GPUs that still run UDSMProt

The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.

What the numbers mean

What it takes to run this model

Minimum card

Tesla C1080

Memory needed

0.7 GB

Fastest

119,710 tok/s

UDSMProt reaches a parameter count of 28.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.

The smallest card that holds it is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 1,302 tokens per second.

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

Background

UDSMProt was published by Fraunhofer Heinrich Hertz Institute, in the country recorded as Germany, during September 2019. It comes out of an organisation categorised as research collective.

It works in the domain of Biology, and is recorded as performing the task of proteins, Protein or nucleotide language model (pLM/nLM), Enzyme function prediction.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached.

Reading the throughput figures

Across every card that can run it, the middle of the range sits at 3,361.4 tokens per second. Exceeding reading speed outright: 818 of them.

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.

What went into building it

Producing it required arithmetic totalling around 6.4 × 10¹⁷ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.

Training consumed a corpus of around 149,700,000 tokens of text.

It is tracked in the underlying dataset for one reason in particular: sOTA improvement.

Step by step

How to choose a GPU for UDSMProt

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

The table lists every card able to hold UDSMProt, needing around 0.7 GB at a compression of Q8_0. That figure, not the headline performance of a card, is what decides whether it runs.
02

Set the context length you will work at

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 UDSMProt.
03

Decide how much compression you will accept

Each card runs the least-compressed copy it can hold, 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

Rank by throughput rather than spec sheet

Ranking by tokens per second follows memory bandwidth rather than core counts, for UDSMProt. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 119,710 tok/s.
05

Look at the headroom, not just the fit

The fit column separates cards that just manage it from those with room to spare, in the case of UDSMProt. 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

Check the card from the other side

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

Answers

UDSMProt — common questions

UDSMProt— 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 0.7 GB and generating roughly 20,051 tokens per second. The fit is comfortable.

UDSMProt— 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.

UDSMProt— how many parameters does it have?

It has a parameter count of 28.3M. Python code: # Given LSTM parameters emb_sz = 400 # embedding size, typically equal to the input size for the first layer nh = 1150 # number of hidden units nl = 3 # number of layers # The formula for a single LSTM layer parameters is: # P = 4 * ((input_dim + hidden_dim) * hidden_dim + hidden_dim) # First layer parameters (input_dim is the embedding size) first_layer_params = 4 * ((emb_sz + nh) * nh + nh) # For subsequent layers, input_dim is equal to hidden_dim (nh) subsequent_layer_params = 4 * ((nh + nh) * nh + nh) # Total parameters for all layers total_params = first_layer_params + (nl - 1) * subsequent_layer_params print(total_params). 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.

UDSMProt— who created it?

It was published by Fraunhofer Heinrich Hertz Institute, based in Germany, an organisation categorised as research collective.

UDSMProt— when was it released?

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

UDSMProt— what is it used for?

It works in the domain of Biology, and is recorded as handling the task of proteins, Protein or nucleotide language model (pLM/nLM), Enzyme function prediction. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

UDSMProt— 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.

UDSMProt— how much compute was used to train it?

Training consumed around 6.4 × 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.

UDSMProt— 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.

UDSMProt— 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.

UDSMProt— 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.

UDSMProt— how accurate are these speed estimates?

They are calculated from specifications rather than measured, and each carries a range. One example: 71,826–191,535 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

UDSMProt— 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 0.7 GB, and produces roughly 1,302 tokens per second. The number of cards able to run it in total: 818.

UDSMProt— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 119,710 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: 818.

UDSMProt— how much VRAM does it need?

It needs about 0.7 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.

UDSMProt— 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 0.7 GB and generating roughly 22,296 tokens per second. The fit is comfortable.

UDSMProt— 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 0.7 GB and generating roughly 13,653 tokens per second. The fit is comfortable.

UDSMProt— 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 0.7 GB and generating roughly 16,909 tokens per second. The fit is comfortable.

Source

Original publication

Record last updated 28 November 2025

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.

All AI models