Falcon-H1 TPS calculator

Open weights Technology Innovation Institute 34B parameters May 2025

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

132 cards that can run it

818 cards we hold specifications for

Smallest card that fits

RTX A4500

20 GB · Q3_K_M · 21.5 tok/s

Fastest card

B200

99.7 tok/s · 180 GB

Which GPUs can run Falcon-H1?

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

132 cards match

Calculating

					Needs	Quantisation	Fit
99.7 tok/s 60–159 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	37.1 GB	Q8_0	Comfortable
99.7 tok/s 60–159 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	37.1 GB	Q8_0	Comfortable
79.6 tok/s 48–127 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	37.1 GB	Q8_0	Comfortable
79.6 tok/s 48–127 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	37.1 GB	Q8_0	Comfortable
63.6 tok/s 38–102 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	37.1 GB	Q8_0	Comfortable
60.9 tok/s 37–97 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	37.1 GB	Q8_0	Comfortable
60.9 tok/s 37–97 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	37.1 GB	Q8_0	Comfortable
58.3 tok/s 35–93 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	37.1 GB	Q8_0	Comfortable
51.7 tok/s 31–83 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	37.1 GB	Q8_0	Comfortable
51.7 tok/s 31–83 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	37.1 GB	Q8_0	Comfortable
51.7 tok/s 31–83 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	37.1 GB	Q8_0	Comfortable
49.1 tok/s 29–79 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	37.1 GB	Q8_0	Comfortable
41.9 tok/s 25–67 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	37.1 GB	Q8_0	Comfortable
41.9 tok/s 25–67 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	37.1 GB	Q8_0	Comfortable
41.9 tok/s 25–67 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	37.1 GB	Q8_0	Comfortable
41.9 tok/s 25–67 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	37.1 GB	Q8_0	Comfortable
41.9 tok/s 25–67 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	37.1 GB	Q8_0	Comfortable
41.6 tok/s 25–67 · low confidence	DRIVE A100 PROD NVIDIA	32 GB	1,870 GB/s	May 2020	25.2 GB	Q5_K_M	Tight
41.6 tok/s 25–67 · low confidence	GRID A100A NVIDIA	32 GB	1,870 GB/s	May 2020	25.2 GB	Q5_K_M	Tight
39.8 tok/s 24–64 · low confidence	GeForce RTX 5090 NVIDIA	32 GB	1,790 GB/s	Jan 2025	25.2 GB	Q5_K_M	Tight
39.8 tok/s 24–64 · low confidence	GeForce RTX 5090 D NVIDIA	32 GB	1,790 GB/s	Jan 2025	25.2 GB	Q5_K_M	Tight
38.5 tok/s 23–62 · low confidence	GeForce RTX 5090 D V2 NVIDIA	24 GB	1,340 GB/s	Aug 2025	21.3 GB	Q4_K_M	Tight
35.1 tok/s 21–56 · low confidence	A30X NVIDIA	24 GB	1,220 GB/s	Apr 2021	21.3 GB	Q4_K_M	Tight
31.9 tok/s 19–51 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	37.1 GB	Q8_0	Comfortable
31.9 tok/s 19–51 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	37.1 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: Technology Innovation Institute
Organisation type: Government
Country: United Arab Emirates
Published: 21 May 2025
Authors: Jingwei Zuo, Maksim Velikanov, Ilyas Chahed, Younes Belkada, Dhia Eddine Rhayem, Guillaume Kunsch, Hakim Hacid, Hamza Yous, Brahim Farhat, Ibrahim Khadraoui, Mugariya Farooq, Giulia Campesan, Ruxandra Cojocaru, Yasser Djilali, Shi Hu, Iheb Chaabane, Puneesh Khanna, Mohamed El Amine Seddik, Ngoc Dung Huynh, Phuc Le Khac, Leen AlQadi, Billel Mokeddem, Mohamed Chami, Abdalgader Abubaker, Mikhail Lubi…

What it does

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

Domain: Language
Task: Language modeling/generation, Question answering, Code 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: 34B
Training data: 18,000,000,000,000 tokens
Batch size: 26,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: 3.7 × 10²⁴ FLOP
How it was established: Operation counting

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: 4,096
Power draw: 5.6 MW

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

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: Falcon-H1: A Family of Hybrid-Head Language Models Redefining Efficiency and Performance
Last updated: 28 November 2025

The extremes

The ten fastest GPUs that run Falcon-H1

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 Falcon-H1

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

Hardware requirements in practice

Minimum card

RTX A4500

Memory needed

17.3 GB

Fastest

99.7 tok/s

Falcon-H1 reaches a parameter count of 34B. 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: 132.

The entry point is RTX A4500, with a memory capacity of 20 GB, running it at a compression of Q3_K_M and producing around 21.5 tokens per second.

The fastest we calculate for it is B200, generating roughly 99.7 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

Background

Falcon-H1 was published by Technology Innovation Institute, in the country recorded as United Arab Emirates, during May 2025. It comes out of an organisation categorised as government.

It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Question answering, Code generation.

Published weights mean the model runs on your machine rather than someone else's, which is what makes the hardware question below answerable at all. On Hugging Face it is published under the organisation tiiuae.

Reading the throughput figures

Half the cards that hold it manage more than 21.2 tokens per second. Producing text faster than most people read it: 103 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.

How it was trained

Producing it required arithmetic totalling around 3.7 × 10²⁴ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. That figure measures what producing the model cost, and has no bearing on how fast it answers.

It was trained on a corpus of about 18,000,000,000,000 tokens of text.

Step by step

How to choose a GPU for Falcon-H1

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

Start from what it actually needs, which is the requirement of Falcon-H1, needing around 17.3 GB at a compression of Q3_K_M. Capacity is the gate — a card either holds it or it does not.
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 Falcon-H1.
03

Decide how much compression you will accept

Compression is what makes a model fit smaller cards, at some cost in accuracy, reaching a compression of Q3_K_M 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

Rank by throughput rather than spec sheet

Sort by speed to see how cards rank for Falcon-H1. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 99.7 tok/s.
05

Read the fit column last

A tight fit runs, but leaves nothing spare for a longer conversation, in the case of Falcon-H1. 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

See what else that card runs

Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond Falcon-H1.

Answers

Falcon-H1 — common questions

Falcon-H1— what is it used for?

It works in the domain of Language, and is recorded as handling the task of language modeling/generation, Question answering, Code generation. These are the areas it was designed around; they describe intent rather than a hard boundary.

Falcon-H1— where can I download it?

Its weights are published on Hugging Face, under the organisation tiiuae. We do not host model files — this site calculates what hardware is needed to run them.

Falcon-H1— how much compute was used to train it?

Training consumed around 3.7 × 10²⁴ FLOP, on hardware recorded as NVIDIA H100 SXM5 80GB. 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.

Falcon-H1— can I run it 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 model is rarely worth using. The nearest miss we calculate falls short by 6.9 GB. Every figure here assumes the whole model is resident on the card.

Falcon-H1— would two GPUs run it faster?

Capacity adds across cards; throughput does not. The number of cards already holding it on their own: 132. So a second card is rarely the answer here.

Falcon-H1— 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: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

Falcon-H1— how accurate are these speed estimates?

Every figure is derived from memory bandwidth and model size, not benchmarked, which is why each is published as a range rather than a single number. One example: 60–159 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

Falcon-H1— what GPU do I need to run it?

The smallest card in our catalogue that holds it is RTX A4500, with a memory capacity of 20 GB. It runs the model at a compression of Q3_K_M using about 17.3 GB, and produces roughly 21.5 tokens per second. The number of cards able to run it in total: 132.

Falcon-H1— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 99.7 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: 103.

Falcon-H1— how much VRAM does it need?

It needs about 17.3 GB at a compression of Q3_K_M, 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.

Falcon-H1— 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 Q4_K_M, using about 21.3 GB and generating roughly 38.5 tokens per second. The fit is tight.

Falcon-H1— 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.

Falcon-H1— how many parameters does it have?

It has a parameter count of 34B. "In this release, we feature six open-weight models: 0.5B, 1.5B, 1.5B-Deep, 3B, 7B, and 34B, along with their instruct versions" (https://huggingface.co/blog/tiiuae/falcon-h1). 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.

Falcon-H1— who created it?

It was published by Technology Innovation Institute, based in United Arab Emirates, an organisation categorised as government.

Falcon-H1— when was it released?

It was published in May 2025.

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.

All AI models