HyenaDNA TPS calculator

Open weights Stanford University,Harvard University,Mila - Quebec AI (originally Montreal Institute for Learning Algorithms),University of Montreal / Université de Montréal 6.6M parameters June 2023

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 · 5,585 tok/s

Fastest card

B200

513,369 tok/s · 180 GB

Which GPUs can run HyenaDNA?

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
513,369 tok/s 308,021–821,390 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	0.7 GB	Q8_0	Comfortable
513,369 tok/s 308,021–821,390 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	0.7 GB	Q8_0	Comfortable
409,938 tok/s 245,963–655,901 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	0.7 GB	Q8_0	Comfortable
409,938 tok/s 245,963–655,901 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	0.7 GB	Q8_0	Comfortable
327,850 tok/s 196,710–524,560 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
313,797 tok/s 188,278–502,075 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	0.7 GB	Q8_0	Comfortable
313,797 tok/s 188,278–502,075 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	0.7 GB	Q8_0	Comfortable
300,321 tok/s 180,193–480,513 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	0.7 GB	Q8_0	Comfortable
266,535 tok/s 159,921–426,456 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
266,535 tok/s 159,921–426,456 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
266,535 tok/s 159,921–426,456 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
252,834 tok/s 151,701–404,535 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
215,615 tok/s 129,369–344,984 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
215,615 tok/s 129,369–344,984 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	0.7 GB	Q8_0	Comfortable
215,615 tok/s 129,369–344,984 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
215,615 tok/s 129,369–344,984 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
215,615 tok/s 129,369–344,984 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
164,175 tok/s 98,505–262,681 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	0.7 GB	Q8_0	Comfortable
164,175 tok/s 98,505–262,681 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	0.7 GB	Q8_0	Comfortable
136,813 tok/s 82,088–218,901 · low confidence	Data Center GPU Max 1550 Intel	128 GB	3,280 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
133,893 tok/s 80,336–214,229 · low confidence	Data Center GPU Max Subsystem Intel	128 GB	3,210 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
130,909 tok/s 78,545–209,455 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	0.7 GB	Q8_0	Comfortable
130,909 tok/s 78,545–209,455 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	0.7 GB	Q8_0	Comfortable
130,909 tok/s 78,545–209,455 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	0.7 GB	Q8_0	Comfortable
130,909 tok/s 78,545–209,455 · 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: Stanford University,Harvard University,Mila - Quebec AI (originally Montreal Institute for Learning Algorithms),University of Montreal / Université de Montréal
Organisation type: Academia,Academia,Academia,Academia
Country: United States of America, Canada
Published: 27 June 2023
Authors: Eric Nguyen, Michael Poli, Marjan Faizi, Armin W. Thomas, Callum Birch Sykes, Michael Wornow, Aman Patel, Clayton Rabideau, Stefano Massaroli, Yoshua Bengio, Stefano Ermon, Stephen A. Baccus, Christopher Ré

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)
Numerical format: FP16

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: 6.6M
Training data: 2,945,000,000 tokens
Epochs: 679.12
Batch size: 64,000,000

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.8 × 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: 8
Wall-clock time: 672 hours (28 days)
Power draw: 6.4 kW
Compute cost: $5,000

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 (restricted use)
Training code: Open source
Hugging Face: LongSafari

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: Confident
Citations: 477

Sources

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

Reference: HyenaDNA: Long-Range Genomic Sequence Modeling at Single Nucleotide Resolution
Last updated: 25 May 2026

The extremes

The ten fastest GPUs that run HyenaDNA

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 HyenaDNA

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

The hardware side

Minimum card

Tesla C1080

Memory needed

0.7 GB

Fastest

513,369 tok/s

HyenaDNA is small enough at 6.6M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

At the low end, a Tesla C1080 handles it — 4 GB, at Q8_0, for about 5,585 tokens per second.

A B200 is the fastest we calculate for it: about 513,369 tokens per second, from 8,000 GB/s of memory bandwidth.

Where it came from

HyenaDNA was published by Stanford University,Harvard University,Mila - Quebec AI (originally Montreal Institute for Learning Algorithms),University of Montreal / Université de Montréal, in United States of America, in June 2023. It comes out of academia,Academia,Academia,Academia.

It works in Biology, and is recorded as doing protein or nucleotide language model (pLM/nLM).

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. It is published under the LongSafari organisation on Hugging Face.

Understanding the speeds

The median result is around 14,415.4 tokens per second; 818 cards produce text faster than most people read it.

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.

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.

How it was trained

Producing it required around 1.8 × 10²¹ FLOP of arithmetic, on NVIDIA A100, which is a statement about the training budget rather than about inference.

Around 2,945,000,000 tokens went into training it.

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

Step by step

How to choose a GPU for HyenaDNA

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

01

Start from the memory column

The table lists every card that can hold HyenaDNA — around 0.7 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
02

Match the context to your actual use

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

Choose how far you will compress it

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

Ranking by tokens per second for HyenaDNA follows memory bandwidth, not core counts, which is why the B200 tops it at 513,369 tok/s.
05

Check the fit verdict before buying

The fit column separates cards that just manage HyenaDNA from those with room to spare. Buy for the second if the context might grow.
06

See what else that card runs

Each card page repeats this sweep for every model we hold. It answers what else the hardware is good for, beyond HyenaDNA.

Answers

HyenaDNA — common questions

Why does the quantisation differ between cards for HyenaDNA?

Each card is shown running the least-compressed copy it can hold, and HyenaDNA appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.

How accurate are these HyenaDNA 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 308,021–821,390 tok/s on the B200 rather than a single number.

What GPU do I need to run HyenaDNA?

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

How fast is HyenaDNA on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 513,369 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 818 of the cards that can run HyenaDNA clear that.

How much VRAM does HyenaDNA need?

About 0.7 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 HyenaDNA on a 8 GB GPU?

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

Can I run HyenaDNA on a 12 GB GPU?

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

Can I run HyenaDNA on a 16 GB GPU?

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

Can I run HyenaDNA on a 24 GB GPU?

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

Is HyenaDNA open source?

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

HyenaDNA has 6.6M parameters. Table A.1 shows details, largest experiment is on far right. 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 HyenaDNA?

HyenaDNA was published by Stanford University,Harvard University,Mila - Quebec AI (originally Montreal Institute for Learning Algorithms),University of Montreal / Université de Montréal, based in United States of America, categorised as academia,Academia,Academia,Academia.

When was HyenaDNA released?

HyenaDNA was published in June 2023. 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 HyenaDNA used for?

HyenaDNA works in Biology, and is recorded as handling protein or nucleotide language model (pLM/nLM). 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 HyenaDNA?

Its weights are published under the LongSafari 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 HyenaDNA?

Around 1.8 × 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 HyenaDNA if it does not fit in my GPU?

Partly. Layers that do not fit sit in system memory and run at a fraction of the speed, so a mostly-offloaded HyenaDNA is rarely worth using. Every figure here assumes the whole model is on the card.

Would two GPUs run HyenaDNA faster?

A second card roughly doubles the memory available but not the generation rate. With 818 cards already able to run HyenaDNA alone, the case for pairing is weak.

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.

All AI models