HuBERT TPS calculator

Open weights Facebook AI Research 1B parameters July 2021

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

Fastest card

B200

3,388 tok/s · 180 GB

Which GPUs can run HuBERT?

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
3,388 tok/s

2,033–5,421 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 1.8 GB Q8_0 Comfortable
3,388 tok/s

2,033–5,421 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 1.8 GB Q8_0 Comfortable
2,706 tok/s

1,623–4,329 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 1.8 GB Q8_0 Comfortable
2,706 tok/s

1,623–4,329 · low confidence

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

1,298–3,462 · low confidence

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

1,243–3,314 · low confidence

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

1,243–3,314 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 1.8 GB Q8_0 Comfortable
1,982 tok/s

1,189–3,171 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 1.8 GB Q8_0 Comfortable
1,759 tok/s

1,055–2,815 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 1.8 GB Q8_0 Comfortable
1,759 tok/s

1,055–2,815 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 1.8 GB Q8_0 Comfortable
1,759 tok/s

1,055–2,815 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 1.8 GB Q8_0 Comfortable
1,669 tok/s

1,001–2,670 · low confidence

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

854–2,277 · low confidence

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

854–2,277 · low confidence

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

854–2,277 · low confidence

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

854–2,277 · low confidence

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

854–2,277 · low confidence

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

650–1,734 · low confidence

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

650–1,734 · low confidence

Radeon Instinct MI250X AMD 128 GB 3,280 GB/s Nov 2021 1.8 GB Q8_0 Comfortable
903 tok/s

542–1,445 · low confidence

Data Center GPU Max 1550 Intel 128 GB 3,280 GB/s Jan 2023 1.8 GB Q8_0 Comfortable
884 tok/s

530–1,414 · low confidence

Data Center GPU Max Subsystem Intel 128 GB 3,210 GB/s Jan 2023 1.8 GB Q8_0 Comfortable
864 tok/s

518–1,382 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 1.8 GB Q8_0 Comfortable
864 tok/s

518–1,382 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 1.8 GB Q8_0 Comfortable
864 tok/s

518–1,382 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 1.8 GB Q8_0 Comfortable
864 tok/s

518–1,382 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 1.8 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
Facebook AI Research
Organisation type
Industry
Country
United States of America, France
Published
27 July 2021
Authors
Wei-Ning Hsu, Benjamin Bolte, Yao-Hung Hubert Tsai, Kushal Lakhotia, Ruslan Salakhutdinov, Abdelrahman Mohamed

What it does

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

Domain
Speech
Task
Speech recognition (ASR)
Approach
Self-supervised learning
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
1B

From abstract: "Using a 1B parameter model, HuBERT shows up to 19% and 13% relative WER reduction on the more challenging dev-other and test-other evaluation subsets"

Training data
864,000,000 tokens

"When the HuBERT model is pre-trained on either the standard Librispeech 960h [24] or the Libri-Light 60k hours [25], it either matches or improves upon the state-of-theart wav2vec 2.0 [6] performance on all fine-tuning subsets of 10mins, 1h, 10h, 100h, and 960h." 1h ~ 13,680 words 13,680 * 60,000 = 820800000

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

GPU NOT SPECIFIED - for the sake of argument I assume something on the order of 1 TFLOP/s Numbers from Section IV part C 0.1 * (960h * 32GPUs + 60000h * 256 GPUs) * 3600s/h * 1 TFLOP/s/GPU

How it was established
Hardware

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

https://github.com/facebookresearch/fairseq/tree/main/examples/hubert fairseq(-py) is MIT-licensed. The license applies to the pre-trained models as well. includes training code

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

Abstract: " the HuBERT model either matches or improves upon the state-ofthe-art wav2vec 2.0 performance on the Librispeech (960h) and Libri-light (60,000h) benchmarks with 10min, 1h, 10h, 100h, and 960h fine-tuning subsets."

Record confidence
Speculative
Citations
4,518

Sources

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

Reference
HuBERT: Self-Supervised Speech Representation Learning by Masked Prediction of Hidden Units
Last updated
25 May 2026

The extremes

What the numbers mean

What you need to run it

Minimum card

Tesla C1080

Memory needed

1.8 GB

Fastest

3,388 tok/s

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

The least hardware that works is a Tesla C1080. Its 4 GB is enough at Q8_0 compression, giving roughly 36.9 tokens per second.

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

What this model is

HuBERT was published by Facebook AI Research, in United States of America, in July 2021. industry is the category the publisher falls under.

It works in Speech, and is recorded as doing speech recognition (ASR).

The weights being open is what puts this page in the calculator rather than only in the catalogue: it is a model you can actually hold.

What decides the speed

Half the cards that hold it manage more than 95.1 tokens per second, and 806 exceed reading speed outright.

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.

Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.

What went into building it

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

The training set ran to roughly 864,000,000 tokens.

Its inclusion criterion is highly cited,SOTA improvement.

Step by step

How to choose a GPU for HuBERT

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

  1. 01

    Read the memory figure first

    Look at what HuBERT actually needs — around 1.8 GB at Q8_0. No amount of processing power compensates for a card that cannot hold it.

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

  3. 03

    Choose how far you will compress it

    The quantisation column varies by card, because a bigger card holds a more accurate copy of HuBERT — Q8_0 on the smallest card that fits. Set a floor to hold the comparison at one level.

  4. 04

    Compare tokens per second, not specifications

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

  5. 05

    Check the fit verdict before buying

    Tight means HuBERT loads and works, with no room to raise the context later. Comfortable means you can. The difference matters more than a few tokens per second.

  6. 06

    Open the card you have settled on

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

Answers

HuBERT — common questions

01

What is HuBERT used for?

HuBERT works in Speech, and is recorded as handling speech recognition (ASR). These are the areas it was designed around; they describe intent rather than a hard boundary.

02

Where can I download HuBERT?

The weights for HuBERT are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.

03

How much compute was used to train HuBERT?

Around 5.5 × 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.

04

Can I run HuBERT if it does not fit in my GPU?

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

05

Would two GPUs run HuBERT faster?

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

06

Why does the quantisation differ between cards for HuBERT?

Because capacity varies, so does how hard HuBERT has to be squeezed — 1 distinct levels appear in the table above. Set a minimum quality to compare at one.

07

How accurate are these HuBERT speed estimates?

They are calculated from specifications rather than measured, and each carries a range — 2,033–5,421 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.

08

What GPU do I need to run HuBERT?

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

09

How fast is HuBERT on a GPU?

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

10

How much VRAM does HuBERT need?

About 1.8 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.

11

Can I run HuBERT on a 8 GB GPU?

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

12

Can I run HuBERT on a 12 GB GPU?

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

13

Can I run HuBERT on a 16 GB GPU?

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

14

Can I run HuBERT on a 24 GB GPU?

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

15

Is HuBERT open source?

Its weights are published, so HuBERT 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.

16

How many parameters does HuBERT have?

HuBERT has 1B parameters. From abstract: "Using a 1B parameter model, HuBERT shows up to 19% and 13% relative WER reduction on the more challenging dev-other and test-other evaluation subsets". 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.

17

Who created HuBERT?

HuBERT was published by Facebook AI Research, based in United States of America, categorised as industry.

18

When was HuBERT released?

HuBERT was published in July 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.

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.