MamayLM 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
Smallest card that fits
Quadro 6000
6 GB · Q3_K_M · 15.5 tok/s
Fastest card
B200
376 tok/s · 180 GB
Which GPUs can run MamayLM?
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 | |||||
|---|---|---|---|---|---|---|---|
|
376
tok/s
226–602 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 10.3 GB | Q8_0 | Comfortable |
|
376
tok/s
226–602 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 10.3 GB | Q8_0 | Comfortable |
|
301
tok/s
180–481 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 10.3 GB | Q8_0 | Comfortable |
|
301
tok/s
180–481 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 10.3 GB | Q8_0 | Comfortable |
|
240
tok/s
144–385 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 10.3 GB | Q8_0 | Comfortable |
|
230
tok/s
138–368 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 10.3 GB | Q8_0 | Comfortable |
|
230
tok/s
138–368 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 10.3 GB | Q8_0 | Comfortable |
|
220
tok/s
132–352 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 10.3 GB | Q8_0 | Comfortable |
|
195
tok/s
117–313 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 10.3 GB | Q8_0 | Comfortable |
|
195
tok/s
117–313 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 10.3 GB | Q8_0 | Comfortable |
|
195
tok/s
117–313 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 10.3 GB | Q8_0 | Comfortable |
|
185
tok/s
111–297 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 10.3 GB | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 10.3 GB | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 10.3 GB | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 10.3 GB | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 10.3 GB | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 10.3 GB | Q8_0 | Comfortable |
|
125
tok/s
75–200 · low confidence |
CMP 170HX 8 GB NVIDIA | 8 GB | 1,490 GB/s | Sep 2021 | 7.2 GB | Q5_K_M | Tight |
|
120
tok/s
72–193 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 10.3 GB | Q8_0 | Comfortable |
|
120
tok/s
72–193 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 10.3 GB | Q8_0 | Comfortable |
|
107
tok/s
64–171 · low confidence |
CMP 170HX 10 GB NVIDIA | 10 GB | 1,560 GB/s | Sep 2021 | 8.2 GB | Q6_K | Tight |
|
100
tok/s
60–161 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 10.3 GB | Q8_0 | Comfortable |
|
98.2
tok/s
59–157 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 10.3 GB | Q8_0 | Comfortable |
|
96.0
tok/s
58–154 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 10.3 GB | Q8_0 | Comfortable |
|
96.0
tok/s
58–154 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 10.3 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
- INSAIT,ETH Zurich
- Organisation type
- Academia,Academia
- Country
- Bulgaria, Switzerland
- Published
- 23 April 2025
- Authors
- Anton Alexandrov, Hannah Yukhymenko, Martin Vechev
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Language modeling/generation, Language 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
- 9B
- Training data
- 8,075,000,000,000 tokens
9B
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
- 4.4 × 10²³ FLOP
Gemma 2 9B pretrain on 8T tokens + MamayLM continual pretrain on 75B tokens. Unclear about SFT compute
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
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
- INSAIT introduces MamayLM-Gemma-2-9B-IT-v0.1, the best performing Ukrainian language model based on google/gemma-2-9b and google/gemma-2-9b-it.
- Last updated
- 8 April 2026
The extremes
The ten fastest GPUs for MamayLM
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 376 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 376 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 301 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 301 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 240 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 230 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 230 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 220 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 195 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 195 tok/s
The smallest GPUs that still run MamayLM
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 5.1 GB · Q3_K_M · tight 24.4 tok/s
- 02 GeForce RTX 3050 6 GB 6 GB · needs 5.1 GB · Q3_K_M · tight 21.3 tok/s
- 03 Arc A380M 6 GB · needs 5.1 GB · Q3_K_M · tight 15.4 tok/s
- 04 GeForce RTX 4050 Max-Q 6 GB · needs 5.1 GB · Q3_K_M · tight 24.4 tok/s
- 05 GeForce RTX 4050 Mobile 6 GB · needs 5.1 GB · Q3_K_M · tight 24.4 tok/s
- 06 Data Center GPU Flex 140 6 GB · needs 5.1 GB · Q3_K_M · tight 15.4 tok/s
- 07 Arc Pro A40 6 GB · needs 5.1 GB · Q3_K_M · tight 15.9 tok/s
- 08 Arc Pro A50 6 GB · needs 5.1 GB · Q3_K_M · tight 15.9 tok/s
- 09 GeForce RTX 3050 Max-Q Refresh 6 GB 6 GB · needs 5.1 GB · Q3_K_M · tight 16.8 tok/s
- 10 GeForce RTX 3050 Mobile Refresh 6 GB 6 GB · needs 5.1 GB · Q3_K_M · tight 21.3 tok/s
What the numbers mean
The hardware side
Minimum card
Quadro 6000
Memory needed
5.1 GB
Fastest
376 tok/s
MamayLM is small enough at 9B parameters that hardware is rarely the obstacle — 582 of the cards we track can run it, including cards several years old.
At the low end, a Quadro 6000 handles it — 6 GB, at Q3_K_M, for about 15.5 tokens per second.
A B200 is the fastest we calculate for it: about 376 tokens per second, from 8,000 GB/s of memory bandwidth.
What this model is
MamayLM was published by INSAIT,ETH Zurich, in Bulgaria, in April 2025. It comes out of academia,Academia.
It works in Language, and is recorded as doing language modeling/generation, Language generation.
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 21.1 tokens per second, and 541 of them clear the ten tokens per second that roughly matches reading speed.
Being dense, it reads all of itself per token, which is why the ordering by speed below follows the ordering by memory bandwidth so closely.
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 around 4.4 × 10²³ FLOP of arithmetic, which is a statement about the training budget rather than about inference.
It was trained on about 8,075,000,000,000 tokens of text.
Step by step
How to choose a GPU for MamayLM
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
Every card here has been checked against MamayLM — around 5.1 GB at 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
Set the context to what you will actually use. The cache grows with the conversation, and it is the usual reason MamayLM stops fitting a card that seemed fine.
-
03
Decide how much compression you will accept
Each card runs the least-compressed copy it can hold — Q3_K_M on the smallest card that fits. Setting a floor drops the cards that only manage MamayLM by squeezing it further than you would want.
-
04
Compare tokens per second, not specifications
Sort by speed to see how cards rank for MamayLM. It will not match a gaming ordering — generation is bound by memory bandwidth, which is why the B200 tops it at 376 tok/s.
-
05
Look at the headroom, not just the fit
Tight means MamayLM 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.
-
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 MamayLM.
Answers
MamayLM — common questions
How fast is MamayLM on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 376 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 541 of the cards that can run MamayLM clear that.
How much VRAM does MamayLM need?
About 5.1 GB at Q3_K_M 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.
Can I run MamayLM on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q5_K_M, using about 7.2 GB and generating roughly 125 tokens per second — a tight fit.
Can I run MamayLM on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 10.3 GB and generating roughly 42.9 tokens per second — a tight fit.
Can I run MamayLM on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 10.3 GB and generating roughly 53.2 tokens per second — a comfortable fit.
Can I run MamayLM on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 10.3 GB and generating roughly 63.1 tokens per second — a comfortable fit.
Is MamayLM open source?
Its weights are published, so MamayLM 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.
How many parameters does MamayLM have?
MamayLM has 9B parameters. 9B. 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.
Who created MamayLM?
MamayLM was published by INSAIT,ETH Zurich, based in Bulgaria, categorised as academia,Academia.
When was MamayLM released?
MamayLM was published in April 2025.
What is MamayLM used for?
MamayLM works in Language, and is recorded as handling language modeling/generation, Language generation. These are the areas it was designed around; they describe intent rather than a hard boundary.
Where can I download MamayLM?
The weights for MamayLM are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train MamayLM?
Around 4.4 × 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.
Can I run MamayLM if it does not fit in my GPU?
It can be split between the card and system memory, but MamayLM generates painfully slowly that way — the nearest miss we calculate is short by 1.6 GB. Nothing on this page assumes offloading.
Would two GPUs run MamayLM faster?
Two cards buy memory rather than speed. That matters for MamayLM only if one card cannot hold it — 582 can, so a second adds little.
Why does the quantisation differ between cards for MamayLM?
A larger card holds a more accurate copy. Across the cards that run MamayLM, 4 compression levels are used; the floor control above pins it to one.
How accurate are these MamayLM 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 226–602 tok/s on the B200 rather than a single number.
What GPU do I need to run MamayLM?
The smallest card in our catalogue that holds MamayLM is the Quadro 6000, with 6 GB of memory. It runs the model at Q3_K_M using about 5.1 GB, and produces roughly 15.5 tokens per second. 582 cards in total can run it.
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.