QVQ TPS calculator

Open weights Alibaba 72B parameters December 2024

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

61 cards that can run it

818 cards we hold specifications for

Smallest card that fits

A100 PCIe 40 GB

40 GB · Q3_K_M · 24.8 tok/s

Fastest card

B200

47.1 tok/s · 180 GB

Which GPUs can run QVQ?

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.

61 cards match

Calculating
Needs Quantisation Fit
47.1 tok/s

28–75 · low confidence

B200 NVIDIA 180 GB 8,000 GB/s Jan 2024 77.8 GB Q8_0 Comfortable
47.1 tok/s

28–75 · low confidence

B300 NVIDIA 288 GB 8,000 GB/s Sep 2025 77.8 GB Q8_0 Comfortable
37.6 tok/s

23–60 · low confidence

Radeon Instinct MI350X AMD 288 GB 8,190 GB/s Jan 2025 77.8 GB Q8_0 Comfortable
37.6 tok/s

23–60 · low confidence

Radeon Instinct MI355X AMD 288 GB 8,190 GB/s Jan 2025 77.8 GB Q8_0 Comfortable
30.1 tok/s

18–48 · low confidence

Radeon Instinct MI300 AMD 128 GB 6,550 GB/s Jan 2023 77.8 GB Q8_0 Comfortable
28.8 tok/s

17–46 · low confidence

H200 NVL NVIDIA 141 GB 4,890 GB/s Nov 2024 77.8 GB Q8_0 Comfortable
28.8 tok/s

17–46 · low confidence

H200 SXM 141 GB NVIDIA 141 GB 4,890 GB/s Nov 2024 77.8 GB Q8_0 Comfortable
28.7 tok/s

17–46 · low confidence

H100 SXM5 80 GB NVIDIA 80 GB 3,360 GB/s Oct 2022 61.0 GB Q6_K Tight
28.7 tok/s

17–46 · low confidence

H800 SXM5 NVIDIA 80 GB 3,360 GB/s Mar 2023 61.0 GB Q6_K Tight
27.5 tok/s

17–44 · low confidence

Radeon Instinct MI325X AMD 256 GB 6,000 GB/s Oct 2024 77.8 GB Q8_0 Comfortable
27.0 tok/s

16–43 · low confidence

GRID A100B NVIDIA 48 GB 1,870 GB/s May 2020 40.1 GB IQ4_XS Tight
24.8 tok/s

15–40 · low confidence

A100 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Jun 2020 35.9 GB Q3_K_M Tight
24.8 tok/s

15–40 · low confidence

A100 SXM4 40 GB NVIDIA 40 GB 1,560 GB/s May 2020 35.9 GB Q3_K_M Tight
24.8 tok/s

15–40 · low confidence

A800 PCIe 40 GB NVIDIA 40 GB 1,560 GB/s Nov 2022 35.9 GB Q3_K_M Tight
24.4 tok/s

15–39 · low confidence

Radeon Instinct MI300A AMD 128 GB 5,325 GB/s Dec 2023 77.8 GB Q8_0 Comfortable
24.4 tok/s

15–39 · low confidence

Radeon Instinct MI300X AMD 192 GB 5,325 GB/s Dec 2023 77.8 GB Q8_0 Comfortable
24.4 tok/s

15–39 · low confidence

Radeon Instinct MI308X AMD 192 GB 5,325 GB/s Dec 2023 77.8 GB Q8_0 Comfortable
23.2 tok/s

14–37 · low confidence

H100 NVL 94 GB NVIDIA 94 GB 3,940 GB/s Mar 2023 77.8 GB Q8_0 Tight
21.2 tok/s

13–34 · low confidence

H100 SXM5 64 GB NVIDIA 64 GB 2,020 GB/s Mar 2023 52.6 GB Q5_K_M Tight
19.8 tok/s

12–32 · low confidence

H100 PCIe 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.8 tok/s

12–32 · low confidence

H100 SXM5 94 GB NVIDIA 94 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.8 tok/s

12–32 · low confidence

H100 SXM5 96 GB NVIDIA 96 GB 3,360 GB/s Mar 2023 77.8 GB Q8_0 Tight
19.4 tok/s

12–31 · low confidence

RTX PRO 5000 Blackwell NVIDIA 48 GB 1,340 GB/s Mar 2025 40.1 GB IQ4_XS Tight
17.4 tok/s

10–28 · low confidence

A100 SXM4 80 GB NVIDIA 80 GB 2,040 GB/s Nov 2020 61.0 GB Q6_K Tight
17.4 tok/s

10–28 · low confidence

A100X NVIDIA 80 GB 2,040 GB/s Jun 2021 61.0 GB Q6_K Tight

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
Alibaba
Organisation type
Industry
Country
China
Published
25 December 2024
Authors
Shuai Bai, Keqin Chen, Xuejing Liu, Jialin Wang, Wenbin Ge, Sibo Song, Kai Dang, Peng Wang, Shijie Wang, Jun Tang, Humen Zhong, Yuanzhi Zhu, Mingkun Yang, Zhaohai Li, Jianqiang Wan, Pengfei Wang, Wei Ding, Zheren Fu, Yiheng Xu, Jiabo Ye, Xi Zhang, Tianbao Xie, Zesen Cheng, Hang Zhang, Zhibo Yang, Haiyang Xu, Junyang Lin

What it does

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

Domain
Language, Vision, Multimodal
Task
Visual question answering, Video description, Language modeling/generation, Translation, Question answering, Character recognition (OCR), Quantitative reasoning
Base model
Qwen2-VL-72B

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
72B
Training data
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 (restricted use)
Training code
Unreleased

https://huggingface.co/Qwen/QVQ-72B-Preview Qwen license (restriction on >100m monthly users)

Hugging Face
Qwen

How it is classified

Labels the source dataset applies when tracking notable models, and how confident it is in the entry.

Record confidence
Confident

Sources

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

Reference
QVQ: To See the World with Wisdom
Last updated
28 November 2025

The extremes

What the numbers mean

What you need to run it

Minimum card

A100 PCIe 40 GB

Memory needed

35.9 GB

Fastest

47.1 tok/s

QVQ reaches a parameter count of 72B. That puts it above consumer hardware, into the range where a card is bought for this purpose rather than repurposed for it. The number of cards we track that can hold it: 61.

The least hardware that works is A100 PCIe 40 GB, with a memory capacity of 40 GB, running it at a compression of Q3_K_M and producing around 24.8 tokens per second.

Top of the range is B200, generating roughly 47.1 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

Background

QVQ was published by Alibaba, in the country recorded as China, during December 2024. The category the publisher falls under is industry.

It works in the domain of Language, Vision, Multimodal, and is recorded as performing the task of visual question answering, Video description, Language modeling/generation, Translation, Question answering, Character recognition (OCR), Quantitative reasoning.

Its starting point was an existing base model, Qwen2-VL-72B. That is the usual way a specialised model is produced.

The weights are published, so it can be downloaded and run on your own hardware indefinitely, offline, with no account attached. On Hugging Face it is published under the organisation Qwen.

Reading the throughput figures

The median result is around 16.6 tokens per second. Producing text faster than most people read it: 51 of them.

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.

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 QVQ

The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.

  1. 01

    Read the memory figure first

    Every card here has been checked against QVQ, needing around 35.9 GB at a compression of Q3_K_M. Capacity is the gate — a card either holds it or it does not.

  2. 02

    Match the context to your actual use

    The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect, because at long context a card that handles short questions easily can be dropped by QVQ.

  3. 03

    Decide how much compression you will accept

    Each card runs the least-compressed copy it can hold, 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.

  4. 04

    Rank by throughput rather than spec sheet

    The speed ordering is effectively an ordering by memory bandwidth, for QVQ. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 47.1 tok/s.

  5. 05

    Look at the headroom, not just the fit

    The fit column separates cards that just manage it from those with room to spare, in the case of QVQ. 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.

  6. 06

    Open the card you have settled on

    Following a card through to its own page shows every other model it can hold, which is the question that follows once you have settled on QVQ.

Answers

QVQ — common questions

01

QVQ— 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: 28–75 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

02

QVQ— what GPU do I need to run it?

The smallest card in our catalogue that holds it is A100 PCIe 40 GB, with a memory capacity of 40 GB. It runs the model at a compression of Q3_K_M using about 35.9 GB, and produces roughly 24.8 tokens per second. The number of cards able to run it in total: 61.

03

QVQ— how fast is it on a GPU?

It depends on the card. The quickest we calculate is B200, at about 47.1 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: 51.

04

QVQ— how much VRAM does it need?

It needs about 35.9 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.

05

QVQ— 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.

06

QVQ— how many parameters does it have?

It has a parameter count of 72B. 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.

07

QVQ— who created it?

It was published by Alibaba, based in China, an organisation categorised as industry.

08

QVQ— when was it released?

It was published in December 2024. Capability per parameter has improved considerably since, so a newer model of the same size is often the better use of the same hardware.

09

QVQ— what is it used for?

It works in the domain of Language, Vision, Multimodal, and is recorded as handling the task of visual question answering, Video description, Language modeling/generation, Translation, Question answering, Character recognition (OCR), Quantitative reasoning. A model can carry several of each, so these are the areas it was built for rather than a limit on what it will attempt.

10

QVQ— where can I download it?

Its weights are published on Hugging Face, under the organisation Qwen. We do not host model files — this site calculates what hardware is needed to run them.

11

QVQ— can I run it if it does not fit in my GPU?

Only by offloading, which is usually a false economy: the part held in system memory drags the whole thing down. The nearest miss we calculate falls short by 15.5 GB. Every figure here assumes the whole model is resident on the card.

12

QVQ— would two GPUs run it faster?

Two cards buy memory rather than speed, which matters only if one card cannot hold it. The number that can: 61. So a second card is rarely the answer here.

13

QVQ— why does the quantisation differ between cards?

A larger card holds a more accurate copy. The number of compression levels used across the cards that run it: 5. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

Source

Original publication

Record last updated 28 November 2025

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.