DINOv2 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 · 32.3 tok/s
Fastest card
B200
2,972 tok/s · 180 GB
Which GPUs can run DINOv2?
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 | |||||
|---|---|---|---|---|---|---|---|
|
2,972
tok/s
1,783–4,755 · low confidence |
B200 NVIDIA | 180 GB | 8,000 GB/s | Jan 2024 | 1.9 GB | Q8_0 | Comfortable |
|
2,972
tok/s
1,783–4,755 · low confidence |
B300 NVIDIA | 288 GB | 8,000 GB/s | Sep 2025 | 1.9 GB | Q8_0 | Comfortable |
|
2,373
tok/s
1,424–3,797 · low confidence |
Radeon Instinct MI350X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.9 GB | Q8_0 | Comfortable |
|
2,373
tok/s
1,424–3,797 · low confidence |
Radeon Instinct MI355X AMD | 288 GB | 8,190 GB/s | Jan 2025 | 1.9 GB | Q8_0 | Comfortable |
|
1,898
tok/s
1,139–3,037 · low confidence |
Radeon Instinct MI300 AMD | 128 GB | 6,550 GB/s | Jan 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,817
tok/s
1,090–2,907 · low confidence |
H200 NVL NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.9 GB | Q8_0 | Comfortable |
|
1,817
tok/s
1,090–2,907 · low confidence |
H200 SXM 141 GB NVIDIA | 141 GB | 4,890 GB/s | Nov 2024 | 1.9 GB | Q8_0 | Comfortable |
|
1,739
tok/s
1,043–2,782 · low confidence |
Radeon Instinct MI325X AMD | 256 GB | 6,000 GB/s | Oct 2024 | 1.9 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
Radeon Instinct MI300A AMD | 128 GB | 5,325 GB/s | Dec 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
Radeon Instinct MI300X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,543
tok/s
926–2,469 · low confidence |
Radeon Instinct MI308X AMD | 192 GB | 5,325 GB/s | Dec 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,464
tok/s
878–2,342 · low confidence |
H100 NVL 94 GB NVIDIA | 94 GB | 3,940 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 PCIe 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 SXM5 80 GB NVIDIA | 80 GB | 3,360 GB/s | Oct 2022 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 SXM5 94 GB NVIDIA | 94 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H100 SXM5 96 GB NVIDIA | 96 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
1,248
tok/s
749–1,997 · low confidence |
H800 SXM5 NVIDIA | 80 GB | 3,360 GB/s | Mar 2023 | 1.9 GB | Q8_0 | Comfortable |
|
950
tok/s
570–1,521 · low confidence |
Radeon Instinct MI250 AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.9 GB | Q8_0 | Comfortable |
|
950
tok/s
570–1,521 · low confidence |
Radeon Instinct MI250X AMD | 128 GB | 3,280 GB/s | Nov 2021 | 1.9 GB | Q8_0 | Comfortable |
|
792
tok/s
475–1,267 · low confidence |
Data Center GPU Max 1550 Intel | 128 GB | 3,280 GB/s | Jan 2023 | 1.9 GB | Q8_0 | Comfortable |
|
775
tok/s
465–1,240 · low confidence |
Data Center GPU Max Subsystem Intel | 128 GB | 3,210 GB/s | Jan 2023 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
A100 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Nov 2020 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
A100X NVIDIA | 80 GB | 2,040 GB/s | Jun 2021 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
A800 SXM4 80 GB NVIDIA | 80 GB | 2,040 GB/s | Aug 2022 | 1.9 GB | Q8_0 | Comfortable |
|
758
tok/s
455–1,213 · low confidence |
H100 CNX NVIDIA | 80 GB | 2,040 GB/s | Mar 2023 | 1.9 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 Research,INRIA
- Organisation type
- Industry,Academia
- Country
- United States of America, France
- Published
- 14 April 2023
- Authors
- Maxime Oquab, Timothée Darcet, Théo Moutakanni, Huy Vo, Marc Szafraniec, Vasil Khalidov, Pierre Fernandez, Daniel Haziza, Francisco Massa, Alaaeldin El-Nouby, Mahmoud Assran, Nicolas Ballas, Wojciech Galuba, Russell Howes, Po-Yao Huang, Shang-Wen Li, Ishan Misra, Michael Rabbat, Vasu Sharma, Gabriel Synnaeve, Hu Xu, Hervé Jegou, Julien Mairal, Patrick Labatut, Armand Joulin, Piotr Bojanowski
What it does
The problem areas the model was built for. A model can carry several of each.
- Domain
- Vision
- Task
- Image representation, Image classification
- Approach
- Self-supervised learning
- Numerical format
- FP16
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
- 1.1B
- Training data
- 36,380,002,816 tokens
1.14B from https://huggingface.co/facebook/dinov2-giant
new dataset - named LVD142M Table 15
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
- 7.4 × 10²¹ FLOP
- How it was established
- Hardware
table 14 22016 * 3600 * 312 * 10 ** 12 * 3/10 = 7.41851136e+21 gpu hours in seconds * flops of A100 * assumed utilization rate
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 A100 SXM4 40 GB
- Compute cost
- $10,204
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
apache 2.0 training code and weights here: https://github.com/facebookresearch/dinov2
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
- Record confidence
- Confident
- Citations
- 8,133
"Our family of models drastically improves over the previous state of the art in self-supervised learning and reaches performance comparable with weakly-supervised features." "Because most SSL methods were developped using ImageNet-1k validation performance as a debugging signal, we also report the top-1 accuracy on ImageNet-ReaL and ImageNet-V2." "For iNaturalist 2018, iNaturalist 2021, and Places205, we train a linear classifier with data augmentations as in Sec. 7.1 We report top-1 accuracy…
Sources
Where this record came from and when it was last checked.
- Reference
- DINOv2: Learning Robust Visual Features without Supervision
- Last updated
- 25 May 2026
The extremes
The ten fastest GPUs that run DINOv2
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 2,972 tok/s
- 02 B200 180 GB · 8,000 GB/s · Q8_0 2,972 tok/s
- 03 Radeon Instinct MI350X 288 GB · 8,190 GB/s · Q8_0 2,373 tok/s
- 04 Radeon Instinct MI355X 288 GB · 8,190 GB/s · Q8_0 2,373 tok/s
- 05 Radeon Instinct MI300 128 GB · 6,550 GB/s · Q8_0 1,898 tok/s
- 06 H200 NVL 141 GB · 4,890 GB/s · Q8_0 1,817 tok/s
- 07 H200 SXM 141 GB 141 GB · 4,890 GB/s · Q8_0 1,817 tok/s
- 08 Radeon Instinct MI325X 256 GB · 6,000 GB/s · Q8_0 1,739 tok/s
- 09 Radeon Instinct MI300A 128 GB · 5,325 GB/s · Q8_0 1,543 tok/s
- 10 Radeon Instinct MI300X 192 GB · 5,325 GB/s · Q8_0 1,543 tok/s
The smallest GPUs that still run DINOv2
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.9 GB · Q8_0 · comfortable 35.7 tok/s
- 02 RTX A400 4 GB · needs 1.9 GB · Q8_0 · comfortable 35.7 tok/s
- 03 RTX 500 Mobile Ada Generation 4 GB · needs 1.9 GB · Q8_0 · comfortable 47.6 tok/s
- 04 GeForce RTX 3050 A Mobile 4 GB · needs 1.9 GB · Q8_0 · comfortable 71.3 tok/s
- 05 Jetson Orin Nano 4 GB 4 GB · needs 1.9 GB · Q8_0 · comfortable 12.7 tok/s
- 06 Radeon RX 6450M 4 GB · needs 1.9 GB · Q8_0 · comfortable 37.1 tok/s
- 07 Radeon RX 6550M 4 GB · needs 1.9 GB · Q8_0 · comfortable 41.7 tok/s
- 08 Radeon RX 6550S 4 GB · needs 1.9 GB · Q8_0 · comfortable 37.1 tok/s
- 09 Arc A310 4 GB · needs 1.9 GB · Q8_0 · comfortable 29.9 tok/s
- 10 Arc Pro A30M 4 GB · needs 1.9 GB · Q8_0 · comfortable 30.9 tok/s
What the numbers mean
The hardware side
Minimum card
Tesla C1080
Memory needed
1.9 GB
Fastest
2,972 tok/s
DINOv2 is small enough at 1.1B 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 32.3 tokens per second.
A B200 is the fastest we calculate for it: about 2,972 tokens per second, from 8,000 GB/s of memory bandwidth.
Where it came from
DINOv2 was published by Facebook AI Research,INRIA, in United States of America, in April 2023. industry,Academia is the category the publisher falls under.
It works in Vision, and is recorded as doing image representation, 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.
Understanding the speeds
The median result is around 83.5 tokens per second; 799 cards produce text faster than most people read it.
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.
Memory here is estimated from size rather than computed from the architecture, which is not recorded for this model — the numbers are indicative rather than exact.
What went into building it
Training it took roughly 7.4 × 10²¹ FLOP of computation, on NVIDIA A100 SXM4 40 GB — a measure of what producing the model cost, not of how fast it answers.
The training set ran to roughly 36,380,002,816 tokens.
It is tracked in the underlying dataset for one reason in particular: sOTA improvement.
Step by step
How to choose a GPU for DINOv2
The table above has already assessed every card we hold specifications for against this model. Getting to your answer takes six steps.
-
01
Read the memory figure first
The table lists every card that can hold DINOv2 — around 1.9 GB at Q8_0. That figure, not the card's headline performance, is what decides whether it runs.
-
02
Set the context length you will work at
Longer conversations cost memory on top of what the weights need. Move the slider to your real working length before trusting any row for DINOv2.
-
03
Decide how much compression you will accept
Compression is what makes DINOv2 fit smaller cards, at some cost in accuracy — Q8_0 on the smallest card that fits. A minimum quality removes the ones that go too far.
-
04
Sort by speed
The speed ordering for DINOv2 is effectively an ordering by memory bandwidth, which is why the B200 tops it at 2,972 tok/s.
-
05
Read the fit column last
A tight fit runs DINOv2 but leaves nothing spare for a longer conversation; comfortable has headroom. If you expect to grow the context, buy for comfortable.
-
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. Worth a look before buying for DINOv2 alone — a card is usually bought for more than one model.
Answers
DINOv2 — common questions
What GPU do I need to run DINOv2?
The smallest card in our catalogue that holds DINOv2 is the Tesla C1080, with 4 GB of memory. It runs the model at Q8_0 using about 1.9 GB, and produces roughly 32.3 tokens per second. 818 cards in total can run it.
How fast is DINOv2 on a GPU?
It depends on the card. The quickest we calculate is a B200 at about 2,972 tokens per second; the slowest that still runs it manages considerably less. Reading speed is around ten tokens per second, and 799 of the cards that can run DINOv2 clear that.
How much VRAM does DINOv2 need?
About 1.9 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 DINOv2 on a 8 GB GPU?
Yes. A CMP 170HX 8 GB with 8 GB runs it at Q8_0, using about 1.9 GB and generating roughly 554 tokens per second — a comfortable fit.
Can I run DINOv2 on a 12 GB GPU?
Yes. A GeForce RTX 3080 Ti with 12 GB runs it at Q8_0, using about 1.9 GB and generating roughly 339 tokens per second — a comfortable fit.
Can I run DINOv2 on a 16 GB GPU?
Yes. A Tesla V100 SXM2 16 GB with 16 GB runs it at Q8_0, using about 1.9 GB and generating roughly 420 tokens per second — a comfortable fit.
Can I run DINOv2 on a 24 GB GPU?
Yes. A GeForce RTX 5090 D V2 with 24 GB runs it at Q8_0, using about 1.9 GB and generating roughly 498 tokens per second — a comfortable fit.
Is DINOv2 open source?
Its weights are published, so DINOv2 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 DINOv2 have?
DINOv2 has 1.1B parameters. 1.14B from https://huggingface.co/facebook/dinov2-giant. 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 DINOv2?
DINOv2 was published by Facebook AI Research,INRIA, based in United States of America, categorised as industry,Academia.
When was DINOv2 released?
DINOv2 was published in April 2023. 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 DINOv2 used for?
DINOv2 works in Vision, and is recorded as handling image representation, Image classification. Models frequently carry more than one of each, and the tags describe purpose rather than capability limits.
Where can I download DINOv2?
The weights for DINOv2 are published, though we do not hold a repository link for it. This site calculates hardware requirements rather than hosting model files.
How much compute was used to train DINOv2?
Around 7.4 × 10²¹ FLOP, on NVIDIA A100 SXM4 40 GB. 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.
Can I run DINOv2 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 DINOv2 is rarely worth using. Every figure here assumes the whole model is on the card.
Would two GPUs run DINOv2 faster?
Capacity adds across cards; throughput does not. Since 818 of the cards we track already hold DINOv2 on their own, a second card is rarely the answer here.
Why does the quantisation differ between cards for DINOv2?
Because capacity varies, so does how hard DINOv2 has to be squeezed — 1 distinct levels appear in the table above. Set a minimum quality to compare at one.
How accurate are these DINOv2 speed estimates?
These are estimates with real error bars. The fastest result here, 1,783–4,755 tok/s on the B200, could reasonably land anywhere in its published range depending on which runtime you use.
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.