ether0 TPS calculator
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 we hold specifications for
Smallest card that fits
Xeon Phi 7120P
16 GB · IQ4_XS · 9.9 tok/s
Fastest card
B200
141 tok/s · 180 GB
Which GPUs can run ether0?
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.
241 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
141
tok/s
85–226 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 26.4 GB | Q8_0 | Comfortable |
|
141
tok/s
85–226 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 26.4 GB | Q8_0 | Comfortable |
|
113
tok/s
68–180 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 26.4 GB | Q8_0 | Comfortable |
|
113
tok/s
68–180 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 26.4 GB | Q8_0 | Comfortable |
|
90.2
tok/s
54–144 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 26.4 GB | Q8_0 | Comfortable |
|
86.3
tok/s
52–138 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 26.4 GB | Q8_0 | Comfortable |
|
86.3
tok/s
52–138 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 26.4 GB | Q8_0 | Comfortable |
|
82.6
tok/s
50–132 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 26.4 GB | Q8_0 | Comfortable |
|
73.3
tok/s
44–117 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 26.4 GB | Q8_0 | Comfortable |
|
73.3
tok/s
44–117 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 26.4 GB | Q8_0 | Comfortable |
|
73.3
tok/s
44–117 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 26.4 GB | Q8_0 | Comfortable |
|
69.5
tok/s
42–111 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 26.4 GB | Q8_0 | Comfortable |
|
59.3
tok/s
36–95 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 26.4 GB | Q8_0 | Comfortable |
|
59.3
tok/s
36–95 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 26.4 GB | Q8_0 | Comfortable |
|
59.3
tok/s
36–95 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 26.4 GB | Q8_0 | Comfortable |
|
59.3
tok/s
36–95 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 26.4 GB | Q8_0 | Comfortable |
|
59.3
tok/s
36–95 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 26.4 GB | Q8_0 | Comfortable |
|
49.0
tok/s
29–78 · low confidence |
Tesla V100 SXM2 16 GB NVIDIA | 16 GB | 1,130 GB/s | Nov 2019 | 13.8 GB | IQ4_XS | Tight |
|
45.2
tok/s
27–72 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 26.4 GB | Q8_0 | Comfortable |
|
45.2
tok/s
27–72 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 26.4 GB | Q8_0 | Comfortable |
|
41.6
tok/s
25–67 · low confidence |
GeForce RTX 5080 NVIDIA | 16 GB | 960 GB/s | Jan 2025 | 13.8 GB | IQ4_XS | Tight |
|
38.9
tok/s
23–62 · low confidence |
Tesla V100 DGXS 16 GB NVIDIA | 16 GB | 897 GB/s | Mar 2018 | 13.8 GB | IQ4_XS | Tight |
|
38.9
tok/s
23–62 · low confidence |
Tesla V100 PCIe 16 GB NVIDIA | 16 GB | 897 GB/s | Jun 2017 | 13.8 GB | IQ4_XS | Tight |
|
38.9
tok/s
23–62 · low confidence |
Tesla V100 SXM2 16 GB NVIDIA | 16 GB | 897 GB/s | Jun 2017 | 13.8 GB | IQ4_XS | Tight |
|
38.8
tok/s
23–62 · low confidence |
GeForce RTX 5070 Ti NVIDIA | 16 GB | 896 GB/s | Feb 2025 | 13.8 GB | IQ4_XS | Tight |
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
- FutureHouse
- Country
- United States of America
- Published
- 5 June 2025
- Authors
- Siddharth Narayanan, James Braza, Albert Bou, Geemi Wellawatte, Mayk Caldas, Ludovico Mitchener, Sam Rodriques, Andrew White
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Materials science, Language
- Task
- Language modeling/generation, Molecular property prediction
- Base model
- Mistral Small 3
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
- 24B
- Training data
- tokens
24B
Reasoning models are large language models that emit a long chain-of-thought before answering, providing both higher accuracy and explicit reasoning for their response. A major question has been whether language model reasoning generalizes beyond mathematics, programming, and logic, where most previous work has focused. We demonstrate that reasoning models can be post-trained for chemistry without additional domain pretraining, and require substantially less data compared to contemporary domain-…
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.
- How it was established
- Hardware
- Fine-tuning compute
- 3.9 × 10²² FLOP
989400000000000 FLOP/GPU/sec * 96 hours * 3600 sec / hour * 384 GPUs * 0.3 [assumed utilization] = 3.9391100928e+22 FLOP "Likely" confidence because I didn't account for SFT training, only RL
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 H100 SXM5 80GB
- Chips used
- 384
- Wall-clock time
- 96 hours
- Power draw
- 526.5 kW
"The seven specialist models were trained using 24-72 Nvidia H100 GPUs each" "The final all-task RL training phase was performed using 384 H100 GPUs, over 4 days" 4 days = 96 hours
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
- futurehouse
apache 2.0 https://huggingface.co/futurehouse/ether0
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- ether0: a scientific reasoning model for chemistry
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run ether0
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.
- 01 B300 288 GB · 8,000 GB/s · Q8_0 141 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 141 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 113 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 113 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 90.2 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 86.3 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 86.3 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 82.6 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 73.3 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 73.3 tok/s
The smallest GPUs that still run ether0
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 Ryzen AI Z2 Extreme GPU 16 GB · needs 13.8 GB · IQ4_XS · tight 8.7 tok/s
- 02 Radeon RX 7700 16 GB · needs 13.8 GB · IQ4_XS · tight 21.0 tok/s
- 03 Arc Pro B50 16 GB · needs 13.8 GB · IQ4_XS · tight 6.3 tok/s
- 04 RTX PRO 2000 Blackwell 16 GB · needs 13.8 GB · IQ4_XS · tight 12.5 tok/s
- 05 Ryzen Z2 Extreme GPU 16 GB · needs 13.8 GB · IQ4_XS · tight 4.3 tok/s
- 06 Radeon RX 9060 XT 16 GB 16 GB · needs 13.8 GB · IQ4_XS · tight 10.9 tok/s
- 07 GeForce RTX 5060 Ti 16 GB 16 GB · needs 13.8 GB · IQ4_XS · tight 19.4 tok/s
- 08 GeForce RTX 5080 Mobile 16 GB · needs 13.8 GB · IQ4_XS · tight 38.8 tok/s
- 09 Radeon RX 9070 16 GB · needs 13.8 GB · IQ4_XS · tight 21.8 tok/s
- 10 Radeon RX 9070 XT 16 GB · needs 13.8 GB · IQ4_XS · tight 21.8 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Xeon Phi 7120P
Memory needed
13.8 GB
Fastest
141 tok/s
ether0 reaches a parameter count of 24B. That lands in the range a serious desktop card can handle once the weights are compressed. The number of cards we track that can run it: 241.
The entry point is Xeon Phi 7120P, with a memory capacity of 16 GB, running it at a compression of IQ4_XS and producing around 9.9 tokens per second.
The quickest result comes from B200, generating roughly 141 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
What this model is
ether0 was published by FutureHouse, in the country recorded as United States of America, during June 2025.
It works in the domain of Materials science, Language, and is recorded as performing the task of language modeling/generation, Molecular property prediction.
Rather than being trained from scratch, it is derived from Mistral Small 3. That is the usual way a specialised model is produced.
The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. On Hugging Face it is published under the organisation futurehouse.
What decides the speed
Half the cards that hold it manage more than 19.4 tokens per second. Clearing the ten tokens per second that roughly matches reading speed: 193 of them.
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.
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.
Step by step
How to choose a GPU for ether0
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 able to hold ether0, needing around 13.8 GB at a compression of IQ4_XS. No amount of processing power compensates for a card that cannot hold it.
-
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, because at long context a card that handles short questions easily can be dropped by ether0.
-
03
Set a quality floor
The quantisation column varies by card, because a bigger card holds a more accurate copy, reaching a compression of IQ4_XS 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.
-
04
Sort by speed
Sort by speed to see how cards rank for ether0. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 141 tok/s.
-
05
Look at the headroom, not just the fit
A tight fit runs, but leaves nothing spare for a longer conversation, in the case of ether0. 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.
-
06
Check the card from the other side
Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond ether0.
Answers
ether0 — common questions
ether0— how accurate are these speed estimates?
These are estimates with real error bars, and any of them could reasonably land anywhere in its published range depending on which runtime you use. The fastest result here: 85–226 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
ether0— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Xeon Phi 7120P, with a memory capacity of 16 GB. It runs the model at a compression of IQ4_XS using about 13.8 GB, and produces roughly 9.9 tokens per second. The number of cards able to run it in total: 241.
ether0— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 141 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: 193.
ether0— how much VRAM does it need?
It needs about 13.8 GB at a compression of IQ4_XS, 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.
ether0— 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 IQ4_XS, using about 13.8 GB and generating roughly 49.0 tokens per second. The fit is tight.
ether0— 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 Q6_K, using about 20.8 GB and generating roughly 34.4 tokens per second. The fit is tight.
ether0— 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.
ether0— how many parameters does it have?
It has a parameter count of 24B. 24B. 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.
ether0— who created it?
It was published by FutureHouse, based in United States of America.
ether0— when was it released?
It was published in June 2025.
ether0— what is it used for?
It works in the domain of Materials science, Language, and is recorded as handling the task of language modeling/generation, Molecular property prediction. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
ether0— where can I download it?
Its weights are published on Hugging Face, under the organisation futurehouse. We do not host model files — this site calculates what hardware is needed to run them.
ether0— can I run it if it does not fit in my GPU?
It can be split between the card and system memory, but it generates painfully slowly that way. The nearest miss we calculate falls short by 4.4 GB. Every figure here assumes the whole model is resident on the card.
ether0— would two GPUs run it faster?
Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 241. So a second card is rarely the answer here.
ether0— why does the quantisation differ between cards?
A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
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.