H-optimus-0 TPS calculator

Open weights 1.1B parameters August 2024

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

Fastest card

B200

3,080 tok/s · 180 GB

Which GPUs can run H-optimus-0?

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

1,848–4,928 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 1.9 GB Q8_0 Comfortable
3,080 tok/s

1,848–4,928 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 1.9 GB Q8_0 Comfortable
2,460 tok/s

1,476–3,935 · low confidence

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

1,476–3,935 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 1.9 GB Q8_0 Comfortable
1,967 tok/s

1,180–3,147 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 1.9 GB Q8_0 Comfortable
1,883 tok/s

1,130–3,012 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 1.9 GB Q8_0 Comfortable
1,883 tok/s

1,130–3,012 · low confidence

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

1,081–2,883 · low confidence

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

960–2,559 · low confidence

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

960–2,559 · low confidence

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

960–2,559 · low confidence

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

910–2,427 · low confidence

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

776–2,070 · low confidence

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

776–2,070 · low confidence

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

776–2,070 · low confidence

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

776–2,070 · low confidence

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

776–2,070 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 1.9 GB Q8_0 Comfortable
985 tok/s

591–1,576 · low confidence

Radeon Instinct MI250 AMD 128 GB 3,280 GB/s Nov 2021 1.9 GB Q8_0 Comfortable
985 tok/s

591–1,576 · low confidence

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

493–1,313 · low confidence

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

482–1,285 · low confidence

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

471–1,257 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 1.9 GB Q8_0 Comfortable
785 tok/s

471–1,257 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 1.9 GB Q8_0 Comfortable
785 tok/s

471–1,257 · low confidence

A800 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Aug 2022 1.9 GB Q8_0 Comfortable
785 tok/s

471–1,257 · low confidence

H100 CNX NVIDIA 80 GB 2,040 GB/s Mar 2023 1.9 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.

Published
2 August 2024
Authors
bioptimus

What it does

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

Domain
Vision, Biology, Medicine

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
1.1B
Training data
tokens

trained on a proprietary collection of more than 500,000 H&E stained whole slide histology images

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

Sources

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

Reference
H-optimus-0
Last updated
28 November 2025

The extremes

What the numbers mean

Hardware requirements in practice

Minimum card

Tesla C1080

Memory needed

1.9 GB

Fastest

3,080 tok/s

H-optimus-0 is small enough at 1.1B parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

The entry point is the Tesla C1080: 4 GB of memory, Q8_0 compression, roughly 33.5 tokens per second.

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

What this model is

H-optimus-0 was published by its authors, in August 2024.

It works in Vision, Biology, Medicine.

Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.

What decides the speed

Across every card that can run it, the middle of the range is about 86.5 tokens per second, and 799 of them clear the ten tokens per second that roughly matches reading speed.

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.

Step by step

How to choose a GPU for H-optimus-0

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

    The table lists every card that can hold H-optimus-0 — around 1.9 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.

  2. 02

    Match the context to your actual use

    The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context H-optimus-0 can slip off a card that handles short questions easily.

  3. 03

    Decide how much compression you will accept

    The quantisation column varies by card, because a bigger card holds a more accurate copy of H-optimus-0 — 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

    Ranking by tokens per second for H-optimus-0 follows memory bandwidth, not core counts, which is why the B200 tops it at 3,080 tok/s.

  5. 05

    Read the fit column last

    The fit column separates cards that just manage H-optimus-0 from those with room to spare. Buy for the second if the context might grow.

  6. 06

    Check the card from the other side

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

Answers

H-optimus-0 — common questions

01

Why does the quantisation differ between cards for H-optimus-0?

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

02

How accurate are these H-optimus-0 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 1,848–4,928 tok/s on the B200 rather than a single number.

03

What GPU do I need to run H-optimus-0?

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

04

How fast is H-optimus-0 on a GPU?

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

05

How much VRAM does H-optimus-0 need?

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

06

Can I run H-optimus-0 on a 8 GB GPU?

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

07

Can I run H-optimus-0 on a 12 GB GPU?

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

08

Can I run H-optimus-0 on a 16 GB GPU?

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

09

Can I run H-optimus-0 on a 24 GB GPU?

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

10

Is H-optimus-0 open source?

Its weights are published, so H-optimus-0 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.

11

How many parameters does H-optimus-0 have?

H-optimus-0 has 1.1B 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.

12

When was H-optimus-0 released?

H-optimus-0 was published in August 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

13

What is H-optimus-0 used for?

H-optimus-0 works in Vision, Biology, Medicine. These are the areas it was designed around; they describe intent rather than a hard boundary.

14

Where can I download H-optimus-0?

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

15

Can I run H-optimus-0 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 H-optimus-0 is rarely worth using. Every figure here assumes the whole model is on the card.

16

Would two GPUs run H-optimus-0 faster?

Two cards buy memory rather than speed. That matters for H-optimus-0 only if one card cannot hold it — 818 can, so a second adds little.

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.