MolmoAct 2 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
Tesla C1080
4 GB · Q3_K_M · 18.1 tok/s
Fastest card
B200
618 tok/s · 180 GB
Which GPUs can run MolmoAct 2?
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 | |||||
|---|---|---|---|---|---|---|---|
|
618
tok/s
371–988 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 6.6 GB | Q8_0 | Comfortable |
|
618
tok/s
371–988 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 6.6 GB | Q8_0 | Comfortable |
|
493
tok/s
296–789 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 6.6 GB | Q8_0 | Comfortable |
|
493
tok/s
296–789 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 6.6 GB | Q8_0 | Comfortable |
|
394
tok/s
237–631 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 6.6 GB | Q8_0 | Comfortable |
|
378
tok/s
227–604 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 6.6 GB | Q8_0 | Comfortable |
|
378
tok/s
227–604 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 6.6 GB | Q8_0 | Comfortable |
|
361
tok/s
217–578 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 6.6 GB | Q8_0 | Comfortable |
|
321
tok/s
192–513 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 6.6 GB | Q8_0 | Comfortable |
|
321
tok/s
192–513 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 6.6 GB | Q8_0 | Comfortable |
|
321
tok/s
192–513 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 6.6 GB | Q8_0 | Comfortable |
|
304
tok/s
183–487 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 6.6 GB | Q8_0 | Comfortable |
|
259
tok/s
156–415 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 6.6 GB | Q8_0 | Comfortable |
|
259
tok/s
156–415 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 6.6 GB | Q8_0 | Comfortable |
|
259
tok/s
156–415 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 6.6 GB | Q8_0 | Comfortable |
|
259
tok/s
156–415 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 6.6 GB | Q8_0 | Comfortable |
|
259
tok/s
156–415 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 6.6 GB | Q8_0 | Comfortable |
|
198
tok/s
119–316 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 6.6 GB | Q8_0 | Comfortable |
|
198
tok/s
119–316 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 6.6 GB | Q8_0 | Comfortable |
|
165
tok/s
99–263 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 6.6 GB | Q8_0 | Comfortable |
|
161
tok/s
97–258 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 6.6 GB | Q8_0 | Comfortable |
|
158
tok/s
95–252 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 6.6 GB | Q8_0 | Comfortable |
|
158
tok/s
95–252 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 6.6 GB | Q8_0 | Comfortable |
|
158
tok/s
95–252 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 6.6 GB | Q8_0 | Comfortable |
|
158
tok/s
95–252 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 6.6 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
- Allen Institute for AI,University of Washington,National University of Singapore,University of Pennsylvania,Johns Hopkins University,Amazon,Cortex AI
- Organisation type
- Research collective,Academia,Academia,Academia,Academia,Industry,Industry
- Country
- United States of America, Singapore
- Published
- 5 April 2026
- Authors
- Haoquan Fang, Jiafei Duan, Donovan Clay, Sam Wang, Shuo Liu, Weikai Huang, Xiang Fan, Wei-Chuan Tsai, Shirui Chen, Yi Ru Wang, Shanli Xing, Jaemin Cho, Jae Sung Park, Ainaz Eftekhar, Peter Sushko, Karen Farley, Angad Wadhwa, Cole Harrison, Winson Han, Ying-Chun Lee, Eli VanderBilt, Rose Hendrix, Suveen Ellawela, Lucas Ngoo, Joyce Chai, Zhongzheng Ren, Ali Farhadi, Dieter Fox, Ranjay Krishna
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision, Language, Robotics
- Task
- Robotic manipulation
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
- 5.5B
- Training data
- tokens
From https://huggingface.co/allenai/MolmoAct2/blob/main/model.safetensors.index.json
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.1 × 10²² FLOP
Estimate from hardware details: 5760 + 2304 + 2304 = GPU hours across pre-training, post-training and fune-tuning. 16-bit tensor precision (BF16 for "most operations" from the paper), 30% utilization assumed.
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
- 64
- Wall-clock time
- 2,304 hours (96 days)
- Power draw
- 87.2 kW
- Cloud vendor
- Cirrascale Cloud Services
- Data centre
- Ai2 Jupiter, Austin, Texas
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)
- Hugging Face
- allenai
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Why it is tracked
- Discretionary
- Record confidence
- Likely
Sources
Where this record came from and when it was last checked.
- Reference
- MolmoAct2: Action Reasoning Models for Real-world Deployment
- Last updated
- 30 July 2026
The extremes
The ten fastest GPUs that run MolmoAct 2
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 618 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 618 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 493 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 493 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 394 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 378 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 378 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 361 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 321 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 321 tok/s
The smallest GPUs that still run MolmoAct 2
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 GeForce RTX 4010 4 GB · needs 3.4 GB · Q3_K_M · tight 20.0 tok/s
- 02 RTX A400 4 GB · needs 3.4 GB · Q3_K_M · tight 20.0 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 3.4 GB · Q3_K_M · tight 26.7 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 3.4 GB · Q3_K_M · tight 40.0 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 3.4 GB · Q3_K_M · tight 7.1 tok/s
- 06 Radeon RX 6450M 4 GB · needs 3.4 GB · Q3_K_M · tight 20.8 tok/s
- 07 Radeon RX 6550M 4 GB · needs 3.4 GB · Q3_K_M · tight 23.4 tok/s
- 08 Radeon RX 6550S 4 GB · needs 3.4 GB · Q3_K_M · tight 20.8 tok/s
- 09 Arc A310 4 GB · needs 3.4 GB · Q3_K_M · tight 16.8 tok/s
- 10 Arc Pro A30M 4 GB · needs 3.4 GB · Q3_K_M · tight 17.3 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
Tesla C1080
Memory needed
3.4 GB
Fastest
618 tok/s
MolmoAct 2 reaches a parameter count of 5.5B. 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: 818.
The entry point is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q3_K_M and producing around 18.1 tokens per second.
The fastest we calculate for it is B200, generating roughly 618 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
Background
MolmoAct 2 was published by Allen Institute for AI,University of Washington,National University of Singapore,University of Pennsylvania,Johns Hopkins University,Amazon,Cortex AI, in the country recorded as United States of America, during April 2026. The publishing organisation is categorised as research collective,Academia,Academia,Academia,Academia,Industry,Industry.
It works in the domain of Vision, Language, Robotics, and is recorded as performing the task of robotic manipulation.
Because its weights were released, nothing about running it depends on a provider staying available — it is yours once downloaded. On Hugging Face it is published under the organisation allenai.
Reading the throughput figures
Half the cards that hold it manage more than 25.8 tokens per second. Exceeding reading speed outright: 759 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.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
What went into building it
Training it took a computation budget of roughly 1.1 × 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.
The reason it appears in this catalogue at all: discretionary.
Step by step
How to choose a GPU for MolmoAct 2
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Check what it needs before anything else
The table lists every card able to hold MolmoAct 2, needing around 3.4 GB at a compression of Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
-
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 a card that seemed fine stops fitting MolmoAct 2.
-
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
The speed ordering is effectively an ordering by memory bandwidth, for MolmoAct 2. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 618 tok/s.
-
05
Check the fit verdict before buying
A tight fit runs, but leaves nothing spare for a longer conversation, in the case of MolmoAct 2. 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
Open the card you have settled on
Each card page repeats this sweep for every model we hold, answering what else the hardware is good for beyond MolmoAct 2.
Answers
MolmoAct 2 — common questions
MolmoAct 2— why does the quantisation differ between cards?
Each card is shown running the least-compressed copy it can hold. The number of distinct compression levels across the cards that fit it: 4. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
MolmoAct 2— 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: 371–988 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
MolmoAct 2— what GPU do I need to run it?
The smallest card in our catalogue that holds it is Tesla C1080, with a memory capacity of 4 GB. It runs the model at a compression of Q3_K_M using about 3.4 GB, and produces roughly 18.1 tokens per second. The number of cards able to run it in total: 818.
MolmoAct 2— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 618 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: 759.
MolmoAct 2— how much VRAM does it need?
It needs about 3.4 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.
MolmoAct 2— 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 Q8_0, using about 6.6 GB and generating roughly 115 tokens per second. The fit is tight.
MolmoAct 2— 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 6.6 GB and generating roughly 70.5 tokens per second. The fit is comfortable.
MolmoAct 2— 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 6.6 GB and generating roughly 87.3 tokens per second. The fit is comfortable.
MolmoAct 2— 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 6.6 GB and generating roughly 103 tokens per second. The fit is comfortable.
MolmoAct 2— 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.
MolmoAct 2— how many parameters does it have?
It has a parameter count of 5.5B. From https://huggingface.co/allenai/MolmoAct2/blob/main/model.safetensors.index.json. 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.
MolmoAct 2— who created it?
It was published by Allen Institute for AI,University of Washington,National University of Singapore,University of Pennsylvania,Johns Hopkins University,Amazon,Cortex AI, based in United States of America, an organisation categorised as research collective,Academia,Academia,Academia,Academia,Industry,Industry.
MolmoAct 2— when was it released?
It was published in April 2026.
MolmoAct 2— what is it used for?
It works in the domain of Vision, Language, Robotics, and is recorded as handling the task of robotic manipulation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
MolmoAct 2— where can I download it?
Its weights are published on Hugging Face, under the organisation allenai. We do not host model files — this site calculates what hardware is needed to run them.
MolmoAct 2— how much compute was used to train it?
Training consumed around 1.1 × 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.
MolmoAct 2— 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. Every figure here assumes the whole model is resident on the card.
MolmoAct 2— would two GPUs run it faster?
A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 818. So a second card is rarely the answer here.
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.