FixRes ResNeXt-101 WSL 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 · Q8_0 · 44.5 tok/s
Fastest card
B200
4,087 tok/s · 180 GB
Which GPUs can run FixRes ResNeXt-101 WSL?
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 | |||||
|---|---|---|---|---|---|---|---|
|
4,087
tok/s
2,452–6,539 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.6 GB | Q8_0 | Comfortable |
|
4,087
tok/s
2,452–6,539 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.6 GB | Q8_0 | Comfortable |
|
3,264
tok/s
1,958–5,222 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.6 GB | Q8_0 | Comfortable |
|
3,264
tok/s
1,958–5,222 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.6 GB | Q8_0 | Comfortable |
|
2,610
tok/s
1,566–4,176 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.6 GB | Q8_0 | Comfortable |
|
2,498
tok/s
1,499–3,997 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.6 GB | Q8_0 | Comfortable |
|
2,498
tok/s
1,499–3,997 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.6 GB | Q8_0 | Comfortable |
|
2,391
tok/s
1,435–3,826 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.6 GB | Q8_0 | Comfortable |
|
2,122
tok/s
1,273–3,395 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.6 GB | Q8_0 | Comfortable |
|
2,122
tok/s
1,273–3,395 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.6 GB | Q8_0 | Comfortable |
|
2,122
tok/s
1,273–3,395 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.6 GB | Q8_0 | Comfortable |
|
2,013
tok/s
1,208–3,221 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.6 GB | Q8_0 | Comfortable |
|
1,717
tok/s
1,030–2,747 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.6 GB | Q8_0 | Comfortable |
|
1,717
tok/s
1,030–2,747 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.6 GB | Q8_0 | Comfortable |
|
1,717
tok/s
1,030–2,747 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.6 GB | Q8_0 | Comfortable |
|
1,717
tok/s
1,030–2,747 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.6 GB | Q8_0 | Comfortable |
|
1,717
tok/s
1,030–2,747 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.6 GB | Q8_0 | Comfortable |
|
1,307
tok/s
784–2,091 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.6 GB | Q8_0 | Comfortable |
|
1,307
tok/s
784–2,091 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.6 GB | Q8_0 | Comfortable |
|
1,089
tok/s
654–1,743 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.6 GB | Q8_0 | Comfortable |
|
1,066
tok/s
640–1,706 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.6 GB | Q8_0 | Comfortable |
|
1,042
tok/s
625–1,668 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.6 GB | Q8_0 | Comfortable |
|
1,042
tok/s
625–1,668 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.6 GB | Q8_0 | Comfortable |
|
1,042
tok/s
625–1,668 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.6 GB | Q8_0 | Comfortable |
|
1,042
tok/s
625–1,668 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.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
- Facebook AI
- Organisation type
- Industry
- Country
- United States of America
- Published
- 14 June 2019
- Authors
- Hugo Touvron, Andrea Vedaldi, Matthijs Douze, Hervé Jégou
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision
- Task
- Image classification
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
- 829M
- Training data
- 940,000,000 tokens
"Conversely, when training a ResNeXt-101 32x48d pre-trained in weakly-supervised fashion on 940 million public images at resolution 224x224 and further optimizing for test resolution 320x320, we obtain a test top-1 accuracy of 86.4% (top-5: 98.0%) (single-crop)"
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 (non-commercial)
- Training code
- Open (non-commercial)
code/weights with non-commercial license: https://github.com/facebookresearch/FixRes?tab=License-1-ov-file#readme
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
- SOTA improvement
- Citations
- 477
"To the best of our knowledge our ResNeXt-101 32x48d surpasses all other models available in the literature"
Sources
Where this record came from and when it was last checked.
- Reference
- Fixing the train-test resolution discrepancy
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run FixRes ResNeXt-101 WSL
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 4,087 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 4,087 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 3,264 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 3,264 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 2,610 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 2,498 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 2,498 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 2,391 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 2,122 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 2,122 tok/s
The smallest GPUs that still run FixRes ResNeXt-101 WSL
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 1.6 GB · Q8_0 · comfortable 49.1 tok/s
- 02 RTX A400 4 GB · needs 1.6 GB · Q8_0 · comfortable 49.1 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.6 GB · Q8_0 · comfortable 65.4 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.6 GB · Q8_0 · comfortable 98.1 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.6 GB · Q8_0 · comfortable 17.4 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.6 GB · Q8_0 · comfortable 51.0 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.6 GB · Q8_0 · comfortable 57.4 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.6 GB · Q8_0 · comfortable 51.0 tok/s
- 09 Arc A310 4 GB · needs 1.6 GB · Q8_0 · comfortable 41.2 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.6 GB · Q8_0 · comfortable 42.5 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla C1080
Memory needed
1.6 GB
Fastest
4,087 tok/s
FixRes ResNeXt-101 WSL reaches a parameter count of 829M. 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.
At the low end it is handled by Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 44.5 tokens per second.
Top of the range is B200, generating roughly 4,087 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.
What this model is
FixRes ResNeXt-101 WSL was published by Facebook AI, in the country recorded as United States of America, during June 2019. The publishing organisation is categorised as industry.
It works in the domain of Vision, and is recorded as performing the task of image classification.
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.
What decides the speed
Across every card that can run it, the middle of the range sits at 114.8 tokens per second. Exceeding reading speed outright: 809 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.
How it was trained
It was trained on a corpus of about 940,000,000 tokens of text.
The reason it appears in this catalogue at all: sOTA improvement.
Step by step
How to choose a GPU for FixRes ResNeXt-101 WSL
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 FixRes ResNeXt-101 WSL, needing around 1.6 GB at a compression of Q8_0. 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 a card that seemed fine stops fitting FixRes ResNeXt-101 WSL.
-
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 Q8_0 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
Compare tokens per second, not specifications
The speed ordering is effectively an ordering by memory bandwidth, for FixRes ResNeXt-101 WSL. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 4,087 tok/s.
-
05
Read the fit column last
The fit column separates cards that just manage it from those with room to spare, in the case of FixRes ResNeXt-101 WSL. 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
Every card name links to its own page, which runs the same calculation across the whole model catalogue. A card is usually bought for more than one model, so it is worth a look before buying for FixRes ResNeXt-101 WSL.
Answers
FixRes ResNeXt-101 WSL — common questions
FixRes ResNeXt-101 WSL— 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.
FixRes ResNeXt-101 WSL— 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. Every figure here assumes the whole model is resident on the card.
FixRes ResNeXt-101 WSL— would two GPUs run it faster?
Capacity adds across cards; throughput does not. The number of cards already holding it on their own: 818. So a second card is rarely the answer here.
FixRes ResNeXt-101 WSL— why does the quantisation differ between cards?
Because capacity varies, so does how hard it has to be squeezed. The number of distinct levels in the table above: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.
FixRes ResNeXt-101 WSL— 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: 2,452–6,539 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.
FixRes ResNeXt-101 WSL— 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 Q8_0 using about 1.6 GB, and produces roughly 44.5 tokens per second. The number of cards able to run it in total: 818.
FixRes ResNeXt-101 WSL— how fast is it on a GPU?
It depends on the card. The quickest we calculate is B200, at about 4,087 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: 809.
FixRes ResNeXt-101 WSL— how much VRAM does it need?
It needs about 1.6 GB at a compression of Q8_0, 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.
FixRes ResNeXt-101 WSL— 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 1.6 GB and generating roughly 761 tokens per second. The fit is comfortable.
FixRes ResNeXt-101 WSL— 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 1.6 GB and generating roughly 466 tokens per second. The fit is comfortable.
FixRes ResNeXt-101 WSL— 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 1.6 GB and generating roughly 577 tokens per second. The fit is comfortable.
FixRes ResNeXt-101 WSL— 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 1.6 GB and generating roughly 685 tokens per second. The fit is comfortable.
FixRes ResNeXt-101 WSL— 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.
FixRes ResNeXt-101 WSL— how many parameters does it have?
It has a parameter count of 829M. 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.
FixRes ResNeXt-101 WSL— who created it?
It was published by Facebook AI, based in United States of America, an organisation categorised as industry.
FixRes ResNeXt-101 WSL— when was it released?
It was published in June 2019. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.
FixRes ResNeXt-101 WSL— what is it used for?
It works in the domain of Vision, and is recorded as handling the task of image classification. These are the areas it was designed around; they describe intent rather than a hard boundary.
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.