ZymCTRL TPS calculator

Open weights Basecamp Research,Friedrich-Alexander-Universität,University of Girona 738M parameters December 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 · 50.0 tok/s

Fastest card

B200

4,591 tok/s · 180 GB

Which GPUs can run ZymCTRL?

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
4,591 tok/s 2,755–7,346 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	1.5 GB	Q8_0	Comfortable
4,591 tok/s 2,755–7,346 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	1.5 GB	Q8_0	Comfortable
3,666 tok/s 2,200–5,866 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	1.5 GB	Q8_0	Comfortable
3,666 tok/s 2,200–5,866 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	1.5 GB	Q8_0	Comfortable
2,932 tok/s 1,759–4,691 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	1.5 GB	Q8_0	Comfortable
2,806 tok/s 1,684–4,490 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	1.5 GB	Q8_0	Comfortable
2,806 tok/s 1,684–4,490 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	1.5 GB	Q8_0	Comfortable
2,686 tok/s 1,611–4,297 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	1.5 GB	Q8_0	Comfortable
2,384 tok/s 1,430–3,814 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	1.5 GB	Q8_0	Comfortable
2,384 tok/s 1,430–3,814 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	1.5 GB	Q8_0	Comfortable
2,384 tok/s 1,430–3,814 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	1.5 GB	Q8_0	Comfortable
2,261 tok/s 1,357–3,618 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	1.5 GB	Q8_0	Comfortable
1,928 tok/s 1,157–3,085 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	1.5 GB	Q8_0	Comfortable
1,928 tok/s 1,157–3,085 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	1.5 GB	Q8_0	Comfortable
1,928 tok/s 1,157–3,085 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	1.5 GB	Q8_0	Comfortable
1,928 tok/s 1,157–3,085 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	1.5 GB	Q8_0	Comfortable
1,928 tok/s 1,157–3,085 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	1.5 GB	Q8_0	Comfortable
1,468 tok/s 881–2,349 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	1.5 GB	Q8_0	Comfortable
1,468 tok/s 881–2,349 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	1.5 GB	Q8_0	Comfortable
1,224 tok/s 734–1,958 · low confidence	Data Center GPU Max 1550 Intel	128 GB	3,280 GB/s	Jan 2023	1.5 GB	Q8_0	Comfortable
1,197 tok/s 718–1,916 · low confidence	Data Center GPU Max Subsystem Intel	128 GB	3,210 GB/s	Jan 2023	1.5 GB	Q8_0	Comfortable
1,171 tok/s 702–1,873 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	1.5 GB	Q8_0	Comfortable
1,171 tok/s 702–1,873 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	1.5 GB	Q8_0	Comfortable
1,171 tok/s 702–1,873 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	1.5 GB	Q8_0	Comfortable
1,171 tok/s 702–1,873 · 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: Basecamp Research,Friedrich-Alexander-Universität,University of Girona
Organisation type: Industry,Academia,Academia
Country: United Kingdom of Great Britain and Northern Ireland, Germany, Spain
Published: 1 December 2022
Authors: Geraldene Munsamy, Sebastian Lindner, Philipp Lorenz, Noelia Ferruz

What it does

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

Domain: Biology
Task: Protein generation

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: 738M
Training data: tokens
Epochs: 8

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: 5.1 × 10²¹ FLOP
How it was established: Hardware

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 A100
Chips used: 48
Power draw: 38.4 kW

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: Unreleased
Hugging Face: AI4PD

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: 34

Sources

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

Reference: ZymCTRL: a conditional language model for the controllable generation of artificial enzymes
Last updated: 1 January 2026

The extremes

The ten fastest GPUs that run ZymCTRL

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 ZymCTRL

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

1.5 GB

Fastest

4,591 tok/s

ZymCTRL is small enough at 738M 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 Q8_0 and producing around 50.0 tokens per second.

At the other end, a B200 generates roughly 4,591 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.

Where it came from

ZymCTRL was published by Basecamp Research,Friedrich-Alexander-Universität,University of Girona, in United Kingdom of Great Britain and Northern Ireland, in December 2022. industry,Academia,Academia is the category the publisher falls under.

It works in Biology, and is recorded as doing protein generation.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. It is published under the AI4PD organisation on Hugging Face.

Understanding the speeds

The median result is around 128.9 tokens per second; 809 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.

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.

Training and provenance

The training run consumed about 5.1 × 10²¹ FLOP, on NVIDIA A100. That figure describes the cost of creating it and has no bearing on how quickly it generates text.

Step by step

How to choose a GPU for ZymCTRL

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

01

Read the memory figure first

The table lists every card that can hold ZymCTRL — around 1.5 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
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 ZymCTRL can slip off a card that handles short questions easily.
03

Decide how much compression you will accept

Compression is what makes ZymCTRL 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

Sort by speed

Sort by speed to see how cards rank for ZymCTRL. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 4,591 tok/s.
05

Look at the headroom, not just the fit

A tight fit runs ZymCTRL but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
06

See what else that card runs

Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for ZymCTRL alone — a card is usually bought for more than one model.

Answers

ZymCTRL — common questions

Can I run ZymCTRL on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.5 GB and generating roughly 524 tokens per second — a comfortable fit.

Can I run ZymCTRL on a 16 GB GPU?

Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.5 GB and generating roughly 648 tokens per second — a comfortable fit.

Can I run ZymCTRL on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.5 GB and generating roughly 769 tokens per second — a comfortable fit.

Is ZymCTRL open source?

Its weights are published, so ZymCTRL 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 ZymCTRL have?

ZymCTRL has 738M parameters. "ZymCTRL contains 36 layers totalling 738M parameters". 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 ZymCTRL?

ZymCTRL was published by Basecamp Research,Friedrich-Alexander-Universität,University of Girona, based in United Kingdom of Great Britain and Northern Ireland, categorised as industry,Academia,Academia.

When was ZymCTRL released?

ZymCTRL was published in December 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.

What is ZymCTRL used for?

ZymCTRL works in Biology, and is recorded as handling protein generation. 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 ZymCTRL?

Its weights are published under the AI4PD 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 ZymCTRL?

Around 5.1 × 10²¹ FLOP, on NVIDIA A100. 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 ZymCTRL if it does not fit in my GPU?

It can be split between the card and system memory, but ZymCTRL generates painfully slowly that way. Nothing on this page assumes offloading.

Would two GPUs run ZymCTRL faster?

Capacity adds across cards; throughput does not. Since 818 of the cards we track already hold ZymCTRL on their own, a second card is rarely the answer here.

Why does the quantisation differ between cards for ZymCTRL?

A larger card holds a more accurate copy. Across the cards that run ZymCTRL, 1 compression levels are used; the floor control above pins it to one.

How accurate are these ZymCTRL speed estimates?

Every figure is derived from memory bandwidth and model size, not benchmarked. That is why each is published as a range such as 2,755–7,346 tok/s on the B200 rather than a single number.

What GPU do I need to run ZymCTRL?

The smallest card in our catalogue that holds ZymCTRL is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.5 GB, and produces roughly 50.0 tokens per second. 818 cards in total can run it.

How fast is ZymCTRL on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 4,591 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 ZymCTRL clear that.

How much VRAM does ZymCTRL need?

About 1.5 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 ZymCTRL on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.5 GB and generating roughly 855 tokens per second — a comfortable fit.

Source

Original publication

Record last updated 1 January 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.

All AI models