NVLM-D 72B TPS calculator

Open weights NVIDIA 72B parameters October 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 NVLM-D 72B?

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
NVIDIA
Organisation type
Industry
Country
United States of America
Published
22 October 2024
Authors
Wenliang Dai, Nayeon Lee, Boxin Wang, Zhuolin Yang, Zihan Liu, Jon Barker, Tuomas Rintamaki, Mohammad Shoeybi, Bryan Catanzaro, Wei Ping

What it does

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

Domain
Vision, Language
Task
Language modeling/generation, Vision-language generation, Question answering, Code generation, Translation, Quantitative reasoning
Base model
Qwen2-72B,InternViT-6B
Numerical format
BF16

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

72B

Training data
57,016,320,000 tokens

Pre-training Global batch size 2,048 Sequence length in the LLM decoder 512 Downsampling of visual tokens 1024->256 # of visual token per tile 256 # of tiles 1 # of training steps 20K 2048 * (512 + 256 * 1) * 20000 = 31,457,280,000 SFT: Global batch size 128 Sequence length in the LLM decoder 3,200 # of visual token per tile 256 # of tiles 6+1 # of training steps 40K 128 * (3200 + 256*7) * 40000 = 25,559,040,000 31,457,280,000 + 25,559,040,000 = 57,016,320,000

Epochs
1

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
3 × 10²⁴ FLOP

Uses Qwen2-72B as a backbone, which trained with 3.02e24 FLOP, as well as InternViT-6B. It's unclear how many FLOP were spent training but probably negligible; e.g. PaLI trained ViT-e with ~4B parameters using 1.07e23 FLOP. Fine-tuning FLOPs: 57,016,320,000 image/text tokens over all stages 6 * 72B * 57,016,320,000 = 2.463e22

How it was established
Operation counting
Fine-tuning compute
2.5 × 10²² FLOP

Fine-tuning FLOPs: 57,016,320,000 image/text tokens over all stages 6 * 72B * 57,016,320,000 = 2.463e22

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
128
Power draw
176.4 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 (non-commercial)
Training code
Open source

https://huggingface.co/nvidia/NVLM-D-72B Creative Commons Attribution: Non-Commercial 4.0 International https://github.com/NVIDIA/Megatron-LM/tree/NVLM-1.0/examples/multimodal/nvlm license for code seems to be Apache 2.0

Hugging Face
nvidia

How it is classified

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

Likely above 10²³ FLOP
Yes
Why it is tracked
SOTA improvement

SOTA on OCRBench and VQAv2

Record confidence
Confident

Sources

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

Reference
NVLM: Open Frontier-Class Multimodal LLMs
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

NVLM-D 72B sits at 72B parameters, which puts it above consumer hardware and into the range where a card is bought for this purpose rather than repurposed for it. 61 of the cards we track can hold it.

The least hardware that works is a A100 PCIe 40 GB. Its 40 GB is enough at Q3_K_M compression, giving roughly 24.8 tokens per second.

A B200 is the fastest we calculate for it: about 47.1 tokens per second, from 8,000 GB/s of memory bandwidth.

Where it came from

NVLM-D 72B was published by NVIDIA, in United States of America, in October 2024. The organisation is categorised as industry.

It works in Vision, Language, and is recorded as doing language modeling/generation, Vision-language generation, Question answering, Code generation, Translation, Quantitative reasoning.

Its starting point was Qwen2-72B,InternViT-6B — most models at this scale are adapted from an existing base rather than built from nothing.

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. It is published under the nvidia organisation on Hugging Face.

Understanding the speeds

Across every card that can run it, the middle of the range is about 16.6 tokens per second, and 51 of them clear the ten tokens per second that roughly matches reading speed.

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.

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.

What went into building it

Training it took roughly 3 × 10²⁴ FLOP of computation, on NVIDIA H100 SXM5 80GB — a measure of what producing the model cost, not of how fast it answers.

The training set ran to roughly 57,016,320,000 tokens.

Its inclusion criterion is sOTA improvement.

Step by step

How to choose a GPU for NVLM-D 72B

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

  1. 01

    Check what it needs before anything else

    Every card here has been checked against NVLM-D 72B — around 35.9 GB at Q3_K_M. Capacity is the gate — a card either holds it or it does not.

  2. 02

    Set the context length you will work at

    The conversation occupies memory too, and grows as it goes. Set the slider to the length you expect: at long context NVLM-D 72B can slip off a card that handles short questions easily.

  3. 03

    Set a quality floor

    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 NVLM-D 72B by squeezing it further than you would want.

  4. 04

    Rank by throughput rather than spec sheet

    Ranking by tokens per second for NVLM-D 72B follows memory bandwidth, not core counts, which is why the B200 tops it at 47.1 tok/s.

  5. 05

    Look at the headroom, not just the fit

    Tight means NVLM-D 72B 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.

  6. 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 NVLM-D 72B.

Answers

NVLM-D 72B — common questions

01

When was NVLM-D 72B released?

NVLM-D 72B was published in October 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.

02

What is NVLM-D 72B used for?

NVLM-D 72B works in Vision, Language, and is recorded as handling language modeling/generation, Vision-language generation, Question answering, Code generation, Translation, Quantitative reasoning. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.

03

Where can I download NVLM-D 72B?

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

04

How much compute was used to train NVLM-D 72B?

Around 3 × 10²⁴ FLOP, on 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.

05

Can I run NVLM-D 72B if it does not fit in my GPU?

It can be split between the card and system memory, but NVLM-D 72B generates painfully slowly that way — the nearest miss we calculate is short by 15.5 GB. Nothing on this page assumes offloading.

06

Would two GPUs run NVLM-D 72B faster?

Capacity adds across cards; throughput does not. Since 61 of the cards we track already hold NVLM-D 72B on their own, a second card is rarely the answer here.

07

Why does the quantisation differ between cards for NVLM-D 72B?

A larger card holds a more accurate copy. Across the cards that run NVLM-D 72B, 5 compression levels are used; the floor control above pins it to one.

08

How accurate are these NVLM-D 72B speed estimates?

They are calculated from specifications rather than measured, and each carries a range — 28–75 tok/s on the B200, for instance. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

09

What GPU do I need to run NVLM-D 72B?

The smallest card in our catalogue that holds NVLM-D 72B is the A100 PCIe 40 GB, with 40 GB of memory. It runs the model at Q3_K_M using about 35.9 GB, and produces roughly 24.8 tokens per second. 61 cards in total can run it.

10

How fast is NVLM-D 72B on a GPU?

It depends on the card. The quickest we calculate is a 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 51 of the cards that can run NVLM-D 72B clear that.

11

How much VRAM does NVLM-D 72B need?

About 35.9 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.

12

Is NVLM-D 72B open source?

Its weights are published, so NVLM-D 72B 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.

13

How many parameters does NVLM-D 72B have?

NVLM-D 72B has 72B parameters. 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.

14

Who created NVLM-D 72B?

NVLM-D 72B was published by NVIDIA, based in United States of America, categorised as industry.

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.