DeBERTaV3large TPS calculator

Open weights Microsoft Research 418M parameters November 2021

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 · 88.2 tok/s

Fastest card

B200

8,106 tok/s · 180 GB

Which GPUs can run DeBERTaV3large?

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
8,106 tok/s 4,864–12,969 · low confidence	B200 NVIDIA	180 GB	8,000 GB/s	Jan 2024	1.1 GB	Q8_0	Comfortable
8,106 tok/s 4,864–12,969 · low confidence	B300 NVIDIA	288 GB	8,000 GB/s	Sep 2025	1.1 GB	Q8_0	Comfortable
6,473 tok/s 3,884–10,356 · low confidence	Radeon Instinct MI350X AMD	288 GB	8,190 GB/s	Jan 2025	1.1 GB	Q8_0	Comfortable
6,473 tok/s 3,884–10,356 · low confidence	Radeon Instinct MI355X AMD	288 GB	8,190 GB/s	Jan 2025	1.1 GB	Q8_0	Comfortable
5,177 tok/s 3,106–8,283 · low confidence	Radeon Instinct MI300 AMD	128 GB	6,550 GB/s	Jan 2023	1.1 GB	Q8_0	Comfortable
4,955 tok/s 2,973–7,928 · low confidence	H200 NVL NVIDIA	141 GB	4,890 GB/s	Nov 2024	1.1 GB	Q8_0	Comfortable
4,955 tok/s 2,973–7,928 · low confidence	H200 SXM 141 GB NVIDIA	141 GB	4,890 GB/s	Nov 2024	1.1 GB	Q8_0	Comfortable
4,742 tok/s 2,845–7,587 · low confidence	Radeon Instinct MI325X AMD	256 GB	6,000 GB/s	Oct 2024	1.1 GB	Q8_0	Comfortable
4,208 tok/s 2,525–6,734 · low confidence	Radeon Instinct MI300A AMD	128 GB	5,325 GB/s	Dec 2023	1.1 GB	Q8_0	Comfortable
4,208 tok/s 2,525–6,734 · low confidence	Radeon Instinct MI300X AMD	192 GB	5,325 GB/s	Dec 2023	1.1 GB	Q8_0	Comfortable
4,208 tok/s 2,525–6,734 · low confidence	Radeon Instinct MI308X AMD	192 GB	5,325 GB/s	Dec 2023	1.1 GB	Q8_0	Comfortable
3,992 tok/s 2,395–6,387 · low confidence	H100 NVL 94 GB NVIDIA	94 GB	3,940 GB/s	Mar 2023	1.1 GB	Q8_0	Comfortable
3,404 tok/s 2,043–5,447 · low confidence	H100 PCIe 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	1.1 GB	Q8_0	Comfortable
3,404 tok/s 2,043–5,447 · low confidence	H100 SXM5 80 GB NVIDIA	80 GB	3,360 GB/s	Oct 2022	1.1 GB	Q8_0	Comfortable
3,404 tok/s 2,043–5,447 · low confidence	H100 SXM5 94 GB NVIDIA	94 GB	3,360 GB/s	Mar 2023	1.1 GB	Q8_0	Comfortable
3,404 tok/s 2,043–5,447 · low confidence	H100 SXM5 96 GB NVIDIA	96 GB	3,360 GB/s	Mar 2023	1.1 GB	Q8_0	Comfortable
3,404 tok/s 2,043–5,447 · low confidence	H800 SXM5 NVIDIA	80 GB	3,360 GB/s	Mar 2023	1.1 GB	Q8_0	Comfortable
2,592 tok/s 1,555–4,148 · low confidence	Radeon Instinct MI250 AMD	128 GB	3,280 GB/s	Nov 2021	1.1 GB	Q8_0	Comfortable
2,592 tok/s 1,555–4,148 · low confidence	Radeon Instinct MI250X AMD	128 GB	3,280 GB/s	Nov 2021	1.1 GB	Q8_0	Comfortable
2,160 tok/s 1,296–3,456 · low confidence	Data Center GPU Max 1550 Intel	128 GB	3,280 GB/s	Jan 2023	1.1 GB	Q8_0	Comfortable
2,114 tok/s 1,268–3,383 · low confidence	Data Center GPU Max Subsystem Intel	128 GB	3,210 GB/s	Jan 2023	1.1 GB	Q8_0	Comfortable
2,067 tok/s 1,240–3,307 · low confidence	A100 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Nov 2020	1.1 GB	Q8_0	Comfortable
2,067 tok/s 1,240–3,307 · low confidence	A100X NVIDIA	80 GB	2,040 GB/s	Jun 2021	1.1 GB	Q8_0	Comfortable
2,067 tok/s 1,240–3,307 · low confidence	A800 SXM4 80 GB NVIDIA	80 GB	2,040 GB/s	Aug 2022	1.1 GB	Q8_0	Comfortable
2,067 tok/s 1,240–3,307 · low confidence	H100 CNX NVIDIA	80 GB	2,040 GB/s	Mar 2023	1.1 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: Microsoft Research
Organisation type: Industry
Country: United States of America
Published: 18 November 2021
Authors: Pengcheng He, Jianfeng Gao, Weizhu Chen

What it does

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

Domain: Language
Task: Question answering, Language modeling/generation

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: 418M
Training data: 42,666,666,667 tokens

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: 1.1 × 10²⁰ FLOP
How it was established: Operation counting

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
Hugging Face: microsoft

How it is classified

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

Record confidence: Likely

Sources

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

Reference: DeBERTaV3: Improving DeBERTa using ELECTRA-Style Pre-Training with Gradient-Disentangled Embedding Sharing
Last updated: 28 November 2025

The extremes

The ten fastest GPUs that run DeBERTaV3large

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 DeBERTaV3large

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

What it takes to run this model

Minimum card

Tesla C1080

Memory needed

1.1 GB

Fastest

8,106 tok/s

DeBERTaV3large reaches a parameter count of 418M. 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.

The smallest card that holds it is Tesla C1080, with a memory capacity of 4 GB, running it at a compression of Q8_0 and producing around 88.2 tokens per second.

The fastest we calculate for it is B200, generating roughly 8,106 tokens per second on the strength of a memory bandwidth of 8,000 GB/s.

What this model is

DeBERTaV3large was published by Microsoft Research, in the country recorded as United States of America, during November 2021. The category the publisher falls under is industry.

It works in the domain of Language, and is recorded as performing the task of question answering, Language modeling/generation.

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. On Hugging Face it is published under the organisation microsoft.

What decides the speed

Across every card that can run it, the middle of the range sits at 227.6 tokens per second. Exceeding reading speed outright: 817 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.

What went into building it

The training run consumed about 1.1 × 10²⁰ FLOP. That figure measures what producing the model cost, and has no bearing on how fast it answers.

The training set ran to roughly 42,666,666,667 tokens of text.

Step by step

How to choose a GPU for DeBERTaV3large

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 DeBERTaV3large, needing around 1.1 GB at a compression of Q8_0. That figure, not the headline performance of a card, is what decides whether it runs.
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 DeBERTaV3large.
03

Choose how far you will compress it

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

Rank by throughput rather than spec sheet

Ranking by tokens per second follows memory bandwidth rather than core counts, for DeBERTaV3large. It will not match a gaming ordering, because generation is bound by memory bandwidth. The card topping the list is B200, at 8,106 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 DeBERTaV3large. 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

See what else that card runs

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 DeBERTaV3large.

Answers

DeBERTaV3large — common questions

DeBERTaV3large— what is it used for?

It works in the domain of Language, and is recorded as handling the task of question answering, Language modeling/generation. These are the areas it was designed around; they describe intent rather than a hard boundary.

DeBERTaV3large— where can I download it?

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

DeBERTaV3large— how much compute was used to train it?

Training consumed around 1.1 × 10²⁰ FLOP. 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.

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

DeBERTaV3large— would two GPUs run it faster?

A second card roughly doubles the memory available but not the generation rate. The number already able to run it alone: 818. So a second card is rarely the answer here.

DeBERTaV3large— 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: 1. Bigger cards get the more accurate version, and the quality floor above pins the comparison to one level.

DeBERTaV3large— how accurate are these speed estimates?

Every figure is derived from memory bandwidth and model size, not benchmarked, which is why each is published as a range rather than a single number. One example: 4,864–12,969 tok/s on B200. The same model and card vary by thirty to fifty per cent depending on the inference software and its version.

DeBERTaV3large— 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.1 GB, and produces roughly 88.2 tokens per second. The number of cards able to run it in total: 818.

DeBERTaV3large— how fast is it on a GPU?

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

DeBERTaV3large— how much VRAM does it need?

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

DeBERTaV3large— 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.1 GB and generating roughly 1,510 tokens per second. The fit is comfortable.

DeBERTaV3large— 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.1 GB and generating roughly 924 tokens per second. The fit is comfortable.

DeBERTaV3large— 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.1 GB and generating roughly 1,145 tokens per second. The fit is comfortable.

DeBERTaV3large— 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.1 GB and generating roughly 1,358 tokens per second. The fit is comfortable.

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

DeBERTaV3large— how many parameters does it have?

It has a parameter count of 418M. from HF "The DeBERTa V3 large model comes with 24 layers and a hidden size of 1024 . Its total parameter number is 418M since we use a vocabulary containing 128K tokens which introduce 131M parameters in the Embedding layer. This model was trained using the 160GB data as DeBERTa V2.". 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.

DeBERTaV3large— who created it?

It was published by Microsoft Research, based in United States of America, an organisation categorised as industry.

DeBERTaV3large— when was it released?

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

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.

All AI models