s1.1 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
RTX A4500
20 GB · Q3_K_M · 22.9 tok/s
Fastest card
B200
106 tok/s · 180 GB
Which GPUs can run s1.1?
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.
132 cards match
Calculating| Needs | Quantisation | Fit | |||||
|---|---|---|---|---|---|---|---|
|
106
tok/s
64–169 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 35.0 GB | Q8_0 | Comfortable |
|
106
tok/s
64–169 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 35.0 GB | Q8_0 | Comfortable |
|
84.6
tok/s
51–135 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 35.0 GB | Q8_0 | Comfortable |
|
84.6
tok/s
51–135 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 35.0 GB | Q8_0 | Comfortable |
|
67.6
tok/s
41–108 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 35.0 GB | Q8_0 | Comfortable |
|
64.7
tok/s
39–104 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 35.0 GB | Q8_0 | Comfortable |
|
64.7
tok/s
39–104 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 35.0 GB | Q8_0 | Comfortable |
|
61.9
tok/s
37–99 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 35.0 GB | Q8_0 | Comfortable |
|
55.0
tok/s
33–88 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 35.0 GB | Q8_0 | Comfortable |
|
55.0
tok/s
33–88 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 35.0 GB | Q8_0 | Comfortable |
|
55.0
tok/s
33–88 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 35.0 GB | Q8_0 | Comfortable |
|
52.2
tok/s
31–83 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
44.5
tok/s
27–71 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 35.0 GB | Q8_0 | Comfortable |
|
40.9
tok/s
25–66 · low confidence |
GeForce RTX 5090 D V2 NVIDIA | 24 GB | 1,340 GB/s | Aug 2025 | 20.1 GB | Q4_K_M | Tight |
|
37.3
tok/s
22–60 · low confidence |
A30X NVIDIA | 24 GB | 1,220 GB/s | Apr 2021 | 20.1 GB | Q4_K_M | Tight |
|
36.0
tok/s
22–58 · low confidence |
DRIVE A100 PROD NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 27.5 GB | Q6_K | Tight |
|
36.0
tok/s
22–58 · low confidence |
GRID A100A NVIDIA | 32 GB | 1,870 GB/s | May 2020 | 27.5 GB | Q6_K | Tight |
|
34.4
tok/s
21–55 · low confidence |
GeForce RTX 5090 NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 27.5 GB | Q6_K | Tight |
|
34.4
tok/s
21–55 · low confidence |
GeForce RTX 5090 D NVIDIA | 32 GB | 1,790 GB/s | Jan 2025 | 27.5 GB | Q6_K | Tight |
|
33.9
tok/s
20–54 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 35.0 GB | Q8_0 | Comfortable |
|
33.9
tok/s
20–54 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 35.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
- Stanford University,University of Washington,Allen Institute for AI,Contextual AI
- Organisation type
- Academia,Academia,Research collective,Industry
- Country
- United States of America
- Published
- 31 January 2025
- Authors
- Niklas Muennighoff, Zitong Yang, Weijia Shi, Xiang Lisa Li, Li Fei-Fei, Hannaneh Hajishirzi, Luke Zettlemoyer, Percy Liang, Emmanuel Candès, Tatsunori Hashimoto
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Language
- Task
- Mathematical reasoning, Language modeling/generation
- Base model
- Qwen2.5 Instruct (32B)
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
- 32B
- Training data
- tokens
- Epochs
- 5
- Batch size
- 16
1000 samples, 4.7M tokens total. From initial collection of 59K questions
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.
- Fine-tuning compute
- 9 × 10¹¹ FLOP
4.7M tokens for 32B model: 4.7 * 32000 * 6 = 902400M FLOP, or 902400000000. Fine-tuned on the s1K-1.1 dataset, which uses the same number of datapoints as s1, but generated using DeepSeek's r1 rather than Google Gemini Flash Thinking (Flash 2.0 preview).
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 NVL
- Chips used
- 16
- Wall-clock time
- 7 hours
- Power draw
- 12.6 kW
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)
How it is classified
Labels the source dataset applies when tracking notable models, and how confident it is in the entry.
- Record confidence
- Confident
- Citations
- 1,219
Sources
Where this record came from and when it was last checked.
- Reference
- s1: Simple test-time scaling
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run s1.1
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 106 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 106 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 84.6 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 84.6 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 67.6 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 64.7 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 64.7 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 61.9 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 55.0 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 55.0 tok/s
The smallest GPUs that still run s1.1
The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.
- 01 RTX 4000 Ada Generation 20 GB · needs 16.3 GB · Q3_K_M · tight 12.9 tok/s
- 02 RTX 4000 SFF Ada Generation 20 GB · needs 16.3 GB · Q3_K_M · tight 10.0 tok/s
- 03 Radeon RX 7900 XT 20 GB · needs 16.3 GB · Q3_K_M · tight 22.3 tok/s
- 04 A10M 20 GB · needs 16.3 GB · Q3_K_M · tight 17.9 tok/s
- 05 GeForce RTX 3080 Ti 20 GB 20 GB · needs 16.3 GB · Q3_K_M · tight 27.2 tok/s
- 06 RTX A4500 20 GB · needs 16.3 GB · Q3_K_M · tight 22.9 tok/s
- 07 Arc Pro B60 24 GB · needs 20.1 GB · Q4_K_M · tight 9.1 tok/s
- 08 GeForce RTX 5090 D V2 24 GB · needs 20.1 GB · Q4_K_M · tight 40.9 tok/s
- 09 RTX PRO 4000 Blackwell SFF 24 GB · needs 20.1 GB · Q4_K_M · tight 13.2 tok/s
- 10 GeForce RTX 5090 Mobile 24 GB · needs 20.1 GB · Q4_K_M · tight 27.4 tok/s
What the numbers mean
Hardware requirements in practice
Minimum card
RTX A4500
Memory needed
16.3 GB
Fastest
106 tok/s
With 32B parameters, s1.1 lands in the range a serious desktop card can handle once the weights are compressed. 132 of the cards we track can run it.
The entry point is the RTX A4500: 20 GB of memory, Q3_K_M compression, roughly 22.9 tokens per second.
Top of the range is the B200, at roughly 106 tokens per second thanks to 8,000 GB/s of bandwidth.
Background
s1.1 was published by Stanford University,University of Washington,Allen Institute for AI,Contextual AI, in United States of America, in January 2025. The organisation is categorised as academia,Academia,Research collective,Industry.
It works in Language, and is recorded as doing mathematical reasoning, Language modeling/generation.
It builds on Qwen2.5 Instruct (32B), which is why it shares that model's general shape and size.
The weights being open is what puts this page in the calculator rather than only in the catalogue: it is a model you can actually hold.
Reading the throughput figures
Across every card that can run it, the middle of the range is about 20.7 tokens per second, and 103 of them clear the ten tokens per second that roughly matches reading speed.
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 s1.1
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
Look at what s1.1 actually needs — around 16.3 GB at Q3_K_M. No amount of processing power compensates for a card that cannot hold it.
-
02
Match the context to your actual use
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for s1.1.
-
03
Choose how far you will compress it
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 s1.1 by squeezing it further than you would want.
-
04
Rank by throughput rather than spec sheet
The speed ordering for s1.1 is effectively an ordering by memory bandwidth, which is why the B200 tops it at 106 tok/s.
-
05
Read the fit column last
Tight means s1.1 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 s1.1.
Answers
s1.1 — common questions
How fast is s1.1 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 106 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 103 of the cards that can run s1.1 clear that.
How much VRAM does s1.1 need?
About 16.3 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 s1.1 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q4_K_M, using about 20.1 GB and generating roughly 40.9 tokens per second — a tight fit.
Is s1.1 open source?
Its weights are published, so s1.1 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 s1.1 have?
s1.1 has 32B parameters. 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 s1.1?
s1.1 was published by Stanford University,University of Washington,Allen Institute for AI,Contextual AI, based in United States of America, categorised as academia,Academia,Research collective,Industry.
When was s1.1 released?
s1.1 was published in January 2025.
What is s1.1 used for?
s1.1 works in Language, and is recorded as handling mathematical reasoning, Language modeling/generation. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download s1.1?
The weights for s1.1 are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
Can I run s1.1 if it does not fit in my GPU?
Only by offloading, which is usually a false economy: the part in system memory drags the whole thing down — the nearest miss we calculate is short by 5.7 GB. Our figures for s1.1 assume it is fully resident.
Would two GPUs run s1.1 faster?
Capacity adds across cards; throughput does not. Since 132 of the cards we track already hold s1.1 on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for s1.1?
Each card is shown running the least-compressed copy it can hold, and s1.1 appears at 5 different compression levels across the cards that fit it. Bigger cards get the more accurate version.
How accurate are these s1.1 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 64–169 tok/s on the B200 rather than a single number.
What GPU do I need to run s1.1?
The smallest card in our catalogue that holds s1.1 is the RTX A4500, with 20 GB of memory. It runs the model at Q3_K_M using about 16.3 GB, and produces roughly 22.9 tokens per second. 132 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.