ProGen2-base TPS calculator

Open weights Salesforce Research,Columbia University,Johns Hopkins University 764M parameters June 2022

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 · 48.3 tok/s

Fastest card

B200

4,435 tok/s · 180 GB

Which GPUs can run ProGen2-base?

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
4,435 tok/s

2,661–7,096 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 1.5 GB Q8_0 Comfortable
4,435 tok/s

2,661–7,096 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 1.5 GB Q8_0 Comfortable
3,541 tok/s

2,125–5,666 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 1.5 GB Q8_0 Comfortable
3,541 tok/s

2,125–5,666 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 1.5 GB Q8_0 Comfortable
2,832 tok/s

1,699–4,532 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 1.5 GB Q8_0 Comfortable
2,711 tok/s

1,626–4,337 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 1.5 GB Q8_0 Comfortable
2,711 tok/s

1,626–4,337 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 1.5 GB Q8_0 Comfortable
2,594 tok/s

1,557–4,151 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 1.5 GB Q8_0 Comfortable
2,303 tok/s

1,382–3,684 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 1.5 GB Q8_0 Comfortable
2,303 tok/s

1,382–3,684 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 1.5 GB Q8_0 Comfortable
2,303 tok/s

1,382–3,684 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 1.5 GB Q8_0 Comfortable
2,184 tok/s

1,311–3,495 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 1.5 GB Q8_0 Comfortable
1,863 tok/s

1,118–2,980 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.5 GB Q8_0 Comfortable
1,863 tok/s

1,118–2,980 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 1.5 GB Q8_0 Comfortable
1,863 tok/s

1,118–2,980 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 1.5 GB Q8_0 Comfortable
1,863 tok/s

1,118–2,980 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 1.5 GB Q8_0 Comfortable
1,863 tok/s

1,118–2,980 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 1.5 GB Q8_0 Comfortable
1,418 tok/s

851–2,269 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 1.5 GB Q8_0 Comfortable
1,418 tok/s

851–2,269 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 1.5 GB Q8_0 Comfortable
1,182 tok/s

709–1,891 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 1.5 GB Q8_0 Comfortable
1,157 tok/s

694–1,851 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 1.5 GB Q8_0 Comfortable
1,131 tok/s

679–1,809 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 1.5 GB Q8_0 Comfortable
1,131 tok/s

679–1,809 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 1.5 GB Q8_0 Comfortable
1,131 tok/s

679–1,809 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 1.5 GB Q8_0 Comfortable
1,131 tok/s

679–1,809 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 1.5 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
Salesforce Research,Columbia University,Johns Hopkins University
Organisation type
Industry,Academia,Academia
Country
United States of America
Published
27 June 2022
Authors
Erik Nijkamp, Jeffrey Ruffolo, Eli N. Weinstein, Nikhil Naik, Ali Madani

What it does

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

Domain
Biology
Task
Protein or nucleotide language model (pLM/nLM)

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

764M (Table1)

Training data
tokens

200B from Table 9 https://www.biorxiv.org/content/10.1101/2023.07.05.547496v1 from Table 1 of the original paper: batch size 500k total steps: 400,000 400,000*500000 / 200000000000 = 1 epoch

Epochs
1

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

Table 9 from here: https://www.biorxiv.org/content/10.1101/2023.07.05.547496v1.full.pdf FLOP estimate: 1.1E+21 6 FLOP / parameter / token * 764*10^6 parameters * 200*10^9 tokens = 9.168e+20 FLOP

How it was established
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
Google TPU v3

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)

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Record confidence
Confident
Citations
507

Sources

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

Reference
ProGen2: Exploring the Boundaries of Protein Language Models
Last updated
25 May 2026

The extremes

What the numbers mean

The hardware side

Minimum card

Tesla C1080

Memory needed

1.5 GB

Fastest

4,435 tok/s

ProGen2-base reaches a parameter count of 764M. 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 48.3 tokens per second.

Top of the range is B200, generating roughly 4,435 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

About this model

ProGen2-base was published by Salesforce Research,Columbia University,Johns Hopkins University, in the country recorded as United States of America, during June 2022. The category the publisher falls under is industry,Academia,Academia.

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

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.

How fast it runs, and why

Half the cards that hold it manage more than 124.5 tokens per second. Producing text faster than most people read it: 809 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.

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

The training run consumed about 1.1 × 10²¹ FLOP, on hardware recorded as Google TPU v3. That figure measures what producing the model cost, and has no bearing on how fast it answers.

Step by step

How to choose a GPU for ProGen2-base

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

  1. 01

    Start from the memory column

    Start from what it actually needs, which is the requirement of ProGen2-base, needing around 1.5 GB at a compression of Q8_0. Capacity is the gate — a card either holds it or it does not.

  2. 02

    Set the context length you will work at

    Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for ProGen2-base.

  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

    Rank by throughput rather than spec sheet

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

  5. 05

    Check the fit verdict before buying

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

Answers

ProGen2-base — common questions

01

ProGen2-base— how much compute was used to train it?

Training consumed around 1.1 × 10²¹ FLOP, on hardware recorded as Google TPU v3. 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.

02

ProGen2-base— 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.

03

ProGen2-base— 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.

04

ProGen2-base— 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.

05

ProGen2-base— how accurate are these speed estimates?

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

06

ProGen2-base— 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.5 GB, and produces roughly 48.3 tokens per second. The number of cards able to run it in total: 818.

07

ProGen2-base— how fast is it on a GPU?

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

08

ProGen2-base— how much VRAM does it need?

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

09

ProGen2-base— 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.5 GB and generating roughly 826 tokens per second. The fit is comfortable.

10

ProGen2-base— 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.5 GB and generating roughly 506 tokens per second. The fit is comfortable.

11

ProGen2-base— 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.5 GB and generating roughly 626 tokens per second. The fit is comfortable.

12

ProGen2-base— 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.5 GB and generating roughly 743 tokens per second. The fit is comfortable.

13

ProGen2-base— 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.

14

ProGen2-base— how many parameters does it have?

It has a parameter count of 764M. 764M (Table1). 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.

15

ProGen2-base— who created it?

It was published by Salesforce Research,Columbia University,Johns Hopkins University, based in United States of America, an organisation categorised as industry,Academia,Academia.

16

ProGen2-base— when was it released?

It was published in June 2022. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

17

ProGen2-base— what is it used for?

It works in the domain of Biology, and is recorded as handling the task of protein or nucleotide language model (pLM/nLM). These are the areas it was designed around; they describe intent rather than a hard boundary.

18

ProGen2-base— 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.

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.