Mamba2-Hybrid 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
Quadro 6000
6 GB · Q3_K_M · 16.1 tok/s
Fastest card
B200
391 tok/s · 180 GB
Which GPUs can run Mamba2-Hybrid?
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.
582 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
391
tok/s
235–626 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 10.0 GB | Q8_0 | Comfortable |
|
391
tok/s
235–626 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 10.0 GB | Q8_0 | Comfortable |
|
312
tok/s
187–500 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 10.0 GB | Q8_0 | Comfortable |
|
312
tok/s
187–500 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 10.0 GB | Q8_0 | Comfortable |
|
250
tok/s
150–400 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 10.0 GB | Q8_0 | Comfortable |
|
239
tok/s
143–383 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 10.0 GB | Q8_0 | Comfortable |
|
239
tok/s
143–383 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 10.0 GB | Q8_0 | Comfortable |
|
229
tok/s
137–366 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 10.0 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 10.0 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 10.0 GB | Q8_0 | Comfortable |
|
203
tok/s
122–325 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 10.0 GB | Q8_0 | Comfortable |
|
193
tok/s
116–308 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 10.0 GB | Q8_0 | Comfortable |
|
164
tok/s
99–263 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 10.0 GB | Q8_0 | Comfortable |
|
164
tok/s
99–263 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 10.0 GB | Q8_0 | Comfortable |
|
164
tok/s
99–263 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 10.0 GB | Q8_0 | Comfortable |
|
164
tok/s
99–263 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 10.0 GB | Q8_0 | Comfortable |
|
164
tok/s
99–263 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 10.0 GB | Q8_0 | Comfortable |
|
130
tok/s
78–208 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 6.9 GB | Q5_K_M | Tight |
|
125
tok/s
75–200 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 10.0 GB | Q8_0 | Comfortable |
|
125
tok/s
75–200 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 10.0 GB | Q8_0 | Comfortable |
|
111
tok/s
67–177 · low confidence |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.0 GB | Q6_K | Tight |
|
104
tok/s
63–167 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 10.0 GB | Q8_0 | Comfortable |
|
102
tok/s
61–163 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 10.0 GB | Q8_0 | Comfortable |
|
99.8
tok/s
60–160 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 10.0 GB | Q8_0 | Comfortable |
|
99.8
tok/s
60–160 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 10.0 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
- NVIDIA
- Organisation type
- Industry
- Country
- United States of America
- Published
- 12 June 2024
- Authors
- Roger Waleffe, Wonmin Byeon, Duncan Riach, Brandon Norick, Vijay Korthikanti, Tri Dao, Albert Gu, Ali Hatamizadeh, Sudhakar Singh, Deepak Narayanan, Garvit Kulshreshtha, Vartika Singh, Jared Casper, Jan Kautz, Mohammad Shoeybi, Bryan Catanzaro
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
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
- 8.7B
- Training data
- tokens
- Batch size
- 4,194,304
Table 6
"On the larger dataset we increase the batch size to 1024" seq length 4096
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
- Operation counting
6ND = 6*8660000000.00 parameters * 3500000000000 tokens = 1.8186 × 10^23
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
- 1,024
- Hardware utilisation
- MFU 29.9%
- Power draw
- 1.4 MW
"When training on NVIDIA H100 GPUs (NVIDIA 2023), with a tensor-parallel size of four and data-parallel size of 256 (1024 total GPUs) (micro batch size 4, global batch size 1024), our Mamba-2-Hybrid achieves an MFU of 29.9%." Model Flop Utilization (MFU)
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/NVIDIA/Megatron-LM/tree/ssm/examples/mamba Apache 2.0 train script: https://github.com/NVIDIA/Megatron-LM/blob/ssm/examples/mamba/train.sh
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Likely above 10²³ FLOP
- Yes
- Record confidence
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- An Empirical Study of Mamba-based Language Models
- Last updated
- 28 November 2025
The extremes
The ten fastest GPUs that run Mamba2-Hybrid
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 391 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 391 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 312 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 312 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 250 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 239 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 239 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 229 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 203 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 203 tok/s
The smallest GPUs that still run Mamba2-Hybrid
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 RTX 1000 Mobile Ada Generation 6 GB · needs 4.9 GB · Q3_K_M · tight 25.3 tok/s
- 02 GeForce RTX 3050 6 GB 6 GB · needs 4.9 GB · Q3_K_M · tight 22.2 tok/s
- 03 Arc A380M 6 GB · needs 4.9 GB · Q3_K_M · tight 16.0 tok/s
- 04 GeForce RTX 4050 Max-Q 6 GB · needs 4.9 GB · Q3_K_M · tight 25.3 tok/s
- 05 GeForce RTX 4050 Mobile 6 GB · needs 4.9 GB · Q3_K_M · tight 25.3 tok/s
- 06 Data Center GPU Flex 140 6 GB · needs 4.9 GB · Q3_K_M · tight 16.0 tok/s
- 07 Arc Pro A40 6 GB · needs 4.9 GB · Q3_K_M · tight 16.5 tok/s
- 08 Arc Pro A50 6 GB · needs 4.9 GB · Q3_K_M · tight 16.5 tok/s
- 09 GeForce RTX 3050 Max-Q Refresh 6 GB 6 GB · needs 4.9 GB · Q3_K_M · tight 17.4 tok/s
- 10 GeForce RTX 3050 Mobile Refresh 6 GB 6 GB · needs 4.9 GB · Q3_K_M · tight 22.2 tok/s
What the numbers mean
What you need to run it
Minimum card
Quadro 6000
Memory needed
4.9 GB
Fastest
391 tok/s
Mamba2-Hybrid reaches a parameter count of 8.7B. That is small enough that hardware is rarely the obstacle, including on cards several years old. The number of cards we track that can run it: 582.
The least hardware that works is Quadro 6000, with a memory capacity of 6 GB, running it at a compression of Q3_K_M and producing around 16.1 tokens per second.
The quickest result comes from B200, generating roughly 391 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
About this model
Mamba2-Hybrid was published by NVIDIA, in the country recorded as United States of America, during June 2024. It comes out of an organisation categorised as industry.
It works in the domain of Language, and is recorded as performing the task of language modeling/generation, Question answering.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded.
How fast it runs, and why
Half the cards that hold it manage more than 22.0 tokens per second. Producing text faster than most people read it: 545 of them.
Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.
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.
Training and provenance
Producing it required arithmetic totalling around 1.8 × 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.
Step by step
How to choose a GPU for Mamba2-Hybrid
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 Mamba2-Hybrid, needing around 4.9 GB at a compression of Q3_K_M. Capacity is the gate — a card either holds it or it does not.
-
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, because at long context a card that handles short questions easily can be dropped by Mamba2-Hybrid.
-
03
Choose how far you will compress it
The quantisation column varies by card, because a bigger card holds a more accurate copy, 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
Ranking by tokens per second follows memory bandwidth rather than core counts, for Mamba2-Hybrid. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 391 tok/s.
-
05
Check the fit verdict before buying
The fit column separates cards that just manage it from those with room to spare, in the case of Mamba2-Hybrid. 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
Following a card through to its own page shows every other model it can hold, which is the question that follows once you have settled on Mamba2-Hybrid.
Answers
Mamba2-Hybrid — common questions
Mamba2-Hybrid— 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. These are the areas it was designed around; they describe intent rather than a hard boundary.
Mamba2-Hybrid— where can I download it?
The weights are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Mamba2-Hybrid— how much compute was used to train it?
Training consumed around 1.8 × 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.
Mamba2-Hybrid— 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 1.4 GB. Every figure here assumes the whole model is resident on the card.
Mamba2-Hybrid— 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: 582. So a second card is rarely the answer here.
Mamba2-Hybrid— 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.
Mamba2-Hybrid— 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: 235–626 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
Mamba2-Hybrid— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Quadro 6000, with a memory capacity of 6 GB. It runs the model at a compression of Q3_K_M using about 4.9 GB, and produces roughly 16.1 tokens per second. The number of cards able to run it in total: 582.
Mamba2-Hybrid— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 391 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: 545.
Mamba2-Hybrid— how much VRAM does it need?
It needs about 4.9 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.
Mamba2-Hybrid— can I run it on a GPU holding 8 GB?
Yes. The card CMP 170HX 8 GB, holding 8 GB, runs it at a compression of Q5_K_M, using about 6.9 GB and generating roughly 130 tokens per second. The fit is tight.
Mamba2-Hybrid— can I run it on a GPU holding 12 GB?
Yes. The card GeForce RTX 3080 Ti, holding 12 GB, runs it at a compression of Q8_0, using about 10.0 GB and generating roughly 44.6 tokens per second. The fit is tight.
Mamba2-Hybrid— 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 Q8_0, using about 10.0 GB and generating roughly 55.3 tokens per second. The fit is comfortable.
Mamba2-Hybrid— 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 Q8_0, using about 10.0 GB and generating roughly 65.5 tokens per second. The fit is comfortable.
Mamba2-Hybrid— 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.
Mamba2-Hybrid— how many parameters does it have?
It has a parameter count of 8.7B. Table 6. 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.
Mamba2-Hybrid— who created it?
It was published by NVIDIA, based in United States of America, an organisation categorised as industry.
Mamba2-Hybrid— when was it released?
It was published in June 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.
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.