ResNeXt-50 TPS calculator

Open weights University of California San Diego,Facebook 25M parameters November 2016

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 that can run it

818 cards we hold specifications for

Smallest card that fits

Tesla C1080

4 GB · Q8_0 · 1,475 tok/s

Fastest card

B200

135,529 tok/s · 180 GB

Which GPUs can run ResNeXt-50?

Set the inputs, read the answer

Context length tokens

A longer conversation needs more memory, which can push this model off smaller cards.

Minimum quality

Hides cards that would only fit the model by compressing it below this point.

Search cards

Card memory

Also show cards that cannot run it

818 cards match

Calculating

					Needs	Quantisation	Fit
135,529 tok/s 81,318–216,847 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	0.7 GB	Q8_0	Comfortable
135,529 tok/s 81,318–216,847 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	0.7 GB	Q8_0	Comfortable
108,224 tok/s 64,934–173,158 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	0.7 GB	Q8_0	Comfortable
108,224 tok/s 64,934–173,158 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	0.7 GB	Q8_0	Comfortable
86,552 tok/s 51,931–138,484 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
82,842 tok/s 49,705–132,548 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	0.7 GB	Q8_0	Comfortable
82,842 tok/s 49,705–132,548 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	0.7 GB	Q8_0	Comfortable
79,285 tok/s 47,571–126,856 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	0.7 GB	Q8_0	Comfortable
70,365 tok/s 42,219–112,584 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
70,365 tok/s 42,219–112,584 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
70,365 tok/s 42,219–112,584 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	0.7 GB	Q8_0	Comfortable
66,748 tok/s 40,049–106,797 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
56,922 tok/s 34,153–91,076 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
56,922 tok/s 34,153–91,076 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	0.7 GB	Q8_0	Comfortable
56,922 tok/s 34,153–91,076 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
56,922 tok/s 34,153–91,076 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
56,922 tok/s 34,153–91,076 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	0.7 GB	Q8_0	Comfortable
43,342 tok/s 26,005–69,348 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	0.7 GB	Q8_0	Comfortable
43,342 tok/s 26,005–69,348 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	0.7 GB	Q8_0	Comfortable
36,119 tok/s 21,671–57,790 · low confidence	Data Center GPU Max 1550 Intel	128 GB	3,280 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
35,348 tok/s 21,209–56,556 · low confidence	Data Center GPU Max Subsystem Intel	128 GB	3,210 GB/s	Jan 2023	0.7 GB	Q8_0	Comfortable
34,560 tok/s 20,736–55,296 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	0.7 GB	Q8_0	Comfortable
34,560 tok/s 20,736–55,296 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	0.7 GB	Q8_0	Comfortable
34,560 tok/s 20,736–55,296 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	0.7 GB	Q8_0	Comfortable
34,560 tok/s 20,736–55,296 · low confidence	H100 CNX NVIDIA	80 GB	2,040 GB/s	Mar 2023	0.7 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: University of California San Diego,Facebook
Organisation type: Academia,Industry
Country: United States of America
Published: 16 November 2016
Authors: Saining Xie, Ross Girshick, Piotr Dollár, Zhuowen Tu, Kaiming He

What it does

The problem areas the model was built for. A model can carry several of each.

Domain: Vision
Task: Image classification
Numerical format: FP32

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: 25M
Training data: 1,280,000 tokens

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

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: Highly cited
Record confidence: Likely
Citations: 11,620

Sources

Where this record came from and when it was last checked.

Reference: Aggregated Residual Transformations for Deep Neural Networks
Last updated: 25 May 2026

The extremes

The ten fastest GPUs that run ResNeXt-50

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.

The smallest GPUs that still run ResNeXt-50

The cheapest route in, by memory capacity. A tight fit runs the model but leaves nothing spare for a longer conversation.

What the numbers mean

The hardware side

Minimum card

Tesla C1080

Memory needed

0.7 GB

Fastest

135,529 tok/s

ResNeXt-50 is small enough at 25M parameters that hardware is rarely the obstacle — 818 of the cards we track can run it, including cards several years old.

At the low end, a Tesla C1080 handles it — 4 GB, at Q8_0, for about 1,475 tokens per second.

At the other end, a B200 generates roughly 135,529 tokens per second on it, on the strength of 8,000 GB/s of memory bandwidth.

What this model is

ResNeXt-50 was published by University of California San Diego,Facebook, in United States of America, in November 2016. The organisation is categorised as academia,Industry.

It works in Vision, and is recorded as doing image classification.

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.

What decides the speed

The median result is around 3,805.7 tokens per second; 818 cards produce text faster than most people read it.

Every weight participates in every token here, so bandwidth is the whole story: the ranking below is effectively a ranking of memory throughput.

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.

How it was trained

The training set ran to roughly 1,280,000 tokens.

Its inclusion criterion is highly cited.

Step by step

How to choose a GPU for ResNeXt-50

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 ResNeXt-50 — around 0.7 GB at 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 ResNeXt-50 stops fitting a card that seemed fine.
03

Choose how far you will compress it

Each card runs the least-compressed copy it can hold — Q8_0 on the smallest card that fits. Setting a floor drops the cards that only manage ResNeXt-50 by squeezing it further than you would want.
04

Sort by speed

The speed ordering for ResNeXt-50 is effectively an ordering by memory bandwidth, which is why the B200 tops it at 135,529 tok/s.
05

Look at the headroom, not just the fit

Tight means ResNeXt-50 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

Every card name links to its own page, which runs the same calculation across the whole model catalogue. Worth a look before buying for ResNeXt-50 alone — a card is usually bought for more than one model.

Answers

ResNeXt-50 — common questions

How accurate are these ResNeXt-50 speed estimates?

These are estimates with real error bars. The fastest result here, 81,318–216,847 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.

What GPU do I need to run ResNeXt-50?

The smallest card in our catalogue that holds ResNeXt-50 is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 0.7 GB, and produces roughly 1,475 tokens per second. 818 cards in total can run it.

How fast is ResNeXt-50 on a GPU?

It depends on the card. The quickest we calculate is a B200 at about 135,529 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 818 of the cards that can run ResNeXt-50 clear that.

How much VRAM does ResNeXt-50 need?

About 0.7 GB at Q8_0 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 ResNeXt-50 on a 8 GB GPU?

Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 0.7 GB and generating roughly 25,242 tokens per second — a comfortable fit.

Can I run ResNeXt-50 on a 12 GB GPU?

Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 0.7 GB and generating roughly 15,457 tokens per second — a comfortable fit.

Can I run ResNeXt-50 on a 16 GB GPU?

Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 0.7 GB and generating roughly 19,144 tokens per second — a comfortable fit.

Can I run ResNeXt-50 on a 24 GB GPU?

Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 0.7 GB and generating roughly 22,701 tokens per second — a comfortable fit.

Is ResNeXt-50 open source?

Its weights are published, so ResNeXt-50 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 ResNeXt-50 have?

ResNeXt-50 has 25M parameters. "If you’re thinking about ResNets, yes, they are related. ResNeXt-50 has 25M parameters (ResNet-50 has 25.5M)." https://towardsdatascience.com/illustrated-10-cnn-architectures-95d78ace614d. 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 ResNeXt-50?

ResNeXt-50 was published by University of California San Diego,Facebook, based in United States of America, categorised as academia,Industry.

When was ResNeXt-50 released?

ResNeXt-50 was published in November 2016. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

What is ResNeXt-50 used for?

ResNeXt-50 works in Vision, and is recorded as handling image classification. These are the areas it was designed around; they describe intent rather than a hard boundary.

Where can I download ResNeXt-50?

The weights for ResNeXt-50 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 ResNeXt-50 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 ResNeXt-50 is rarely worth using. Every figure here assumes the whole model is on the card.

Would two GPUs run ResNeXt-50 faster?

Two cards buy memory rather than speed. That matters for ResNeXt-50 only if one card cannot hold it — 818 can, so a second adds little.

Why does the quantisation differ between cards for ResNeXt-50?

Each card is shown running the least-compressed copy it can hold, and ResNeXt-50 appears at 1 different compression levels across the cards that fit it. Bigger cards get the more accurate version.

Source

Original publication

Record last updated 25 May 2026

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.

All AI models