Calculate the TPS of the Quadro RTX 5000 X2 Mobile on local AI models
Every model in our catalogue assessed against this card at the context length and minimum quality you choose. Speed is an estimate for a single request, calculated from this card's memory bandwidth and the size of each model once compressed.
Calculated for this card
721 models in our catalogue altogether
Largest model it holds
Nemotron 3-Nano-30B-A3B
31.6B · Q3_K_M · 90.0 tok/s
Fastest model
Gemma 3 QAT 1B
190 tok/s · 1B
Which AI models can run on a Quadro RTX 5000 X2 Mobile?
Set the inputs, read the answer
More context means more memory for the conversation cache. Speed is for a fresh conversation and does not change with this setting.
Hides models that would only fit by being compressed below this point.
455 models match
Calculating| Quantisation | Fit | ||||||
|---|---|---|---|---|---|---|---|
|
190
tok/s
161–228 |
Gemma 3 1B | 1B | Mar 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
190
tok/s
161–228 |
Gemma 3 QAT 1B | 1B | Apr 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
190
tok/s
114–304 · low confidence |
HGRN 1B (WT 103) ≈ | 1B | Nov 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
190
tok/s
114–304 · low confidence |
LLama 3..2 Typhoon 2 1B ≈ | 1B | Dec 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
190
tok/s
114–304 · low confidence |
OLMo-1B ≈ | 1B | Feb 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
190
tok/s
114–304 · low confidence |
Pythia-1b ≈ | 1B | Apr 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
176
tok/s
105–281 · low confidence |
OpenELM-1.1B ≈ | 1.1B | May 2024 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
172
tok/s
104–276 · low confidence |
DeciCoder-1B ≈ | 1.1B | Aug 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
172
tok/s
104–276 · low confidence |
SantaCoder ≈ | 1.1B | Jan 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
172
tok/s
104–276 · low confidence |
TinyLlama-1.1B (1T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
172
tok/s
104–276 · low confidence |
TinyLlama-1.1B (3T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
EXAONE 4.0 (1.2B) ≈ | 1.2B | Jul 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
LFM2-1.2B ≈ | 1.2B | Jul 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
MinerU2.5 ≈ | 1.2B | Sep 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
Pleias 1.0 1.2B ≈ | 1.2B | Dec 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
158
tok/s
95–253 · low confidence |
Pleias-RAG-1B ≈ | 1.2B | Apr 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
154
tok/s
131–185 |
Llama 3.2 1B | 1.2B | Sep 2024 | 2.2 GB | 131k tokens | Q8_0 | Comfortable |
|
152
tok/s
91–243 · low confidence |
MiniCPM-1.2B ≈ | 1.2B | Jun 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
DeepSeek Coder 1.3B ≈ | 1.3B | Jan 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
DeepSeek-VL-1.3B ≈ | 1.3B | Mar 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
DigiRL ≈ | 1.3B | Jun 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
GLA Transformer 1.3B ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
Janus 1.3B ≈ | 1.3B | Oct 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
Kosmos-2.5 ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
146
tok/s
88–234 · low confidence |
Otter ≈ | 1.3B | May 2023 | 2.1 GB | 131k tokens ? | 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
Quadro RTX 5000 X2 Mobile full specification
Everything on record for this board, ordered by how much it bears on running a language model rather than by how a spec sheet would list it. Memory comes first because it decides the outcome; the rest is context.
Memory
The two specifications that decide what this card can run and how quickly. Capacity sets which models fit; bandwidth sets how many tokens per second they produce once they do.
- Memory size
- 16 GB
- Memory bandwidth
- 448 GB/s
- Memory type
- GDDR6
- Memory bus width
- 256 bit
- Memory clock
- 1.75 GHz
The chip
Which processor is on the board and how it was manufactured. A smaller process size generally means more performance for the same power.
- Graphics processor
- TU104
- Architecture
- Turing
- Generation
- Quadro Turing-M(Tx000)
- Foundry
- TSMC
- Process size
- 12 nm
- Transistors
- 13.6 billion
- Transistor density
- 25,000 K/mm²
- Die size
- 545 mm²
- Package
- BGA-2228
- Released
- 8 June 2020
Clock speeds
How fast the processor runs. Worth far less here than on a gaming benchmark: generating text is limited by memory bandwidth, so a higher clock barely moves the result.
- Base clock
- 1.04 GHz
- Boost clock
- 1.53 GHz
Processing units
What the chip contains. These drive graphics performance and matter mainly for processing a long prompt rather than for producing the answer.
- Shading units
- 3,072
- Texture mapping units
- 192
- Render output units
- 64
- Streaming multiprocessors
- 48
- Tensor cores
- 384
- Ray tracing cores
- 48
- L1 cache
- 64 KB
- L2 cache
- 4 MB
Theoretical performance
Peak arithmetic rates published for the board. These are ceilings that no real workload reaches, and generating text reaches a small fraction of them because it is limited by memory rather than arithmetic.
- Half precision (FP16)
- 18.8 TFLOPS
- Single precision (FP32)
- 9.4 TFLOPS
- Double precision (FP64)
- 293.8 GFLOPS
- Pixel rate
- 98 GPixel/s
- Texture rate
- 294 GTexel/s
The board
What it takes to physically install and power the card — the practical constraints that decide whether it fits the machine you already own.
- Power draw (TDP)
- 110 W
- Power connectors
- None
- Bus interface
- PCIe 3.0 x16
- Slot width
- IGP
Software support
Which graphics and compute interfaces the card supports. CUDA compute capability is the one that bears on inference: below 7.0 there are no tensor cores, and modern inference software falls back to slower code paths.
- CUDA compute capability
- 7.5
- DirectX
- 12.2
- OpenGL
- 4.6
- Vulkan
- 1.4
- OpenCL
- 3.0
- Shader model
- 6.8
Listings
Where to buy a Quadro RTX 5000 X2 Mobile
No vendor is currently listing this card. Listings come from vendors who publish them here directly — browse the vendor directory to see who is selling what.
What the numbers mean
Capacity and bandwidth
Memory
16 GB
Bandwidth
448 GB/s
Largest model
Nemotron 3-Nano-30B-A3B
Quadro RTX 5000 X2 Mobile carries 16 GB of GDDR6. That reaches comfortably into small and mid-sized models, though the largest stay out of reach without splitting them. Driver overhead leaves roughly 14.4 GB.
Memory bandwidth reaches 448 GB/s across a bus of 256 bits. That is the number governing generation speed — arithmetic per byte read is small enough that the bus, not the cores, is what everything waits on.
That comes from a memory clock of 1.75 GHz. Both halves matter, and neither is visible in a gaming benchmark.
The practical ceiling is Nemotron 3-Nano-30B-A3B, 31.6B, compressed to Q3_K_M and generating around 90.0 tokens per second.
The chip and how it was built
Quadro RTX 5000 X2 Mobile is built on the graphics processor TU104, using the architecture Turing from NVIDIA, as part of the generation Quadro Turing-M(Tx000).
The chip is manufactured by TSMC, on a process of 12 nm, with a die measuring 545 mm², holding 13.6 billion transistors. A smaller process generally means more performance for the same power, though for language models it matters far less than the memory subsystem.
It was released in June 2020, roughly 6.2678581264254 years ago. Inference software support tends to follow hardware by a year or two, so a card of this age generally has mature, well-optimised code paths available to it.
Compute throughput, and why it matters less than it looks
FP16
18.8 TFLOPS
FP64
293.8 GFLOPS
Tensor cores
384
On paper Quadro RTX 5000 X2 Mobile reaches 18.8 TFLOPS at half precision, and 9.4 TFLOPS at single precision. These are peak figures no real workload sustains, and generating text reaches only a small fraction of them — decoding is limited by memory rather than arithmetic, which is why a card can look enormously powerful here and still produce tokens at an ordinary rate.
Double-precision throughput reaches 293.8 GFLOPS. It has no bearing on running a language model — no inference runtime uses it — but it separates datacentre parts from consumer ones, since the latter deliberately restrict it.
The card carries 384 tensor cores across 48 streaming multiprocessors. These accelerate the matrix arithmetic at the heart of a transformer, and they are what make prompt processing — reading a long document before answering — dramatically faster than it would otherwise be.
Clocks run from a base of 1.04 GHz to a boost of 1.53 GHz. Worth far less here than on a gaming benchmark: raising the clock speeds up the arithmetic, and the arithmetic is not what generation is waiting on.
Cache and processing units
Quadro RTX 5000 X2 Mobile has an L1 cache of 64 KB, backed by an L2 cache of 4 MB. Cache absorbs a share of the memory traffic that would otherwise hit the main bus, which is the one place on this page where a number other than bandwidth quietly affects generation speed — a large L2 lets more of the working set stay close to the cores.
There are 3,072 shading units, 192 texture mapping units, and 64 render output units. These drive graphics workloads and contribute to prompt processing, but they sit idle for much of the time a model spends generating a reply.
Power, size and installation
Power draw
110 W
Quadro RTX 5000 X2 Mobile is rated at 110 W. Running a language model keeps a card busy in bursts rather than continuously — it draws hard while generating and idles between requests — so sustained draw over a working day is usually well below the rated figure.
The board occupies igp. Worth checking against the case and power supply already in the machine, since the largest cards need considerably more of both than a typical desktop provides.
It connects over PCIe 3.0 x16. The interface governs how quickly a model is loaded from disk into the card, not how fast it runs once there, so a narrower link costs a few seconds at startup and nothing thereafter.
The extremes
The largest AI models that run on a Quadro RTX 5000 X2 Mobile
The biggest open-weight models that fit on this card, newest first. Each is shown at the best compression the card can hold.
The fastest AI models on a Quadro RTX 5000 X2 Mobile
Where this card produces tokens quickest. Smaller models dominate here, because generating each token means reading the whole model out of memory once.
Step by step
How to work out the tokens per second of a Quadro RTX 5000 X2 Mobile
You do not have to calculate anything by hand — the gputps.com calculator on this page has already worked it out for every model this card can hold. Reading off the answer takes six steps.
-
01
Start with the model, not the specification
The table lists 455 models this card runs. Search narrows the list by name or by size.
-
02
Set the context length you will actually use
Drag the slider to the conversation length you plan to work at. The cache grows with the conversation, and against a card holding 16 GB that is frequently the difference between a model fitting and not.
-
03
Pin the comparison to one quality level
Each model is shown at the best compression this card can hold. A minimum quality hides the ones that only fit by being squeezed further than you would accept.
-
04
Look at the range, not just the number
Each speed is an estimate for a single conversation, with a range beneath it. The top end here is 190 tok/s on Gemma 3 QAT 1B. The same card and model vary by thirty to fifty per cent between inference runtimes.
-
05
Read the fit verdict last
The fit column separates models that just fit from those with room to spare — worth checking before settling on one, against an available 16 GB.
-
06
Open the model to compare cards
Following a model through to its own page lists all the hardware that can run it, so you can see how it compares against Quadro RTX 5000 X2 Mobile.
Answers
Quadro RTX 5000 X2 Mobile — common questions
Quadro RTX 5000 X2 Mobile— what type of memory does it use?
It uses GDDR6 clocked at 1.75 GHz. HBM types are found on datacentre accelerators and carry far more bandwidth than the GDDR used on desktop cards, which is why they generate tokens considerably faster at the same capacity.
Quadro RTX 5000 X2 Mobile— who makes it?
This is a product of NVIDIA, with the chip manufactured by TSMC, on a process of 12 nm.
Quadro RTX 5000 X2 Mobile— when was it released?
It was released in June 2020.
Quadro RTX 5000 X2 Mobile— how much power does it use?
Rated board power is 110 W. Generating text draws hard in bursts and idles between requests, so average consumption over a working session is normally well below the rated figure.
Quadro RTX 5000 X2 Mobile— how much cache does it have?
The L1 cache is 64 KB, and the L2 cache is 4 MB. Cache absorbs part of the memory traffic that would otherwise reach the main bus, so a larger L2 gives a modest lift to generation speed beyond what bandwidth alone predicts.
Quadro RTX 5000 X2 Mobile— what are its TFLOPS?
It is rated at 18.8 TFLOPS at half precision and 9.4 TFLOPS at single precision. These are peak arithmetic ceilings rather than achievable rates, and text generation reaches only a small fraction of them because it is limited by memory bandwidth instead.
Quadro RTX 5000 X2 Mobile— how many tensor cores does it have?
It has 384 tensor cores across 48 streaming multiprocessors. They accelerate the matrix arithmetic a transformer is built from, which mainly speeds up processing a long prompt rather than producing the reply.
Quadro RTX 5000 X2 Mobile— does it support CUDA?
Yes. It reports CUDA compute capability 7.5. Capability 7.0 and above has tensor cores, which modern inference software uses; below that it falls back to slower code paths for quantised models.
Quadro RTX 5000 X2 Mobile— what bus interface does it use?
It uses PCIe 3.0 x16. This governs how fast a model is loaded onto the card rather than how fast it runs once loaded, so it costs a few seconds at startup and nothing during generation.
Quadro RTX 5000 X2 Mobile— is it good for running local AI models?
Its memory covers small and mid-sized models, though the largest are out of reach and its bandwidth gives usable, if unspectacular, generation speeds. In total it runs 455 of the models we track. Whether that is enough depends entirely on which model you want — the table above answers that directly.
Quadro RTX 5000 X2 Mobile— can it run a model that does not fit in its memory?
Offloading past the card's 16 GB drags the whole thing down, and none of the figures on this page assume it.
Would two Quadro RTX 5000 X2 Mobile cards be twice as fast?
No. A second card doubles the memory to 32 GB which lets you hold models neither could hold alone, but generation does not split that way. These figures describe one card.
Quadro RTX 5000 X2 Mobile— which AI models can it run?
455 of the 721 open-weight language models we track fit on this card and can be run locally. The table on this page lists every one, with the memory it needs, the quantisation it runs at and an estimated generation speed.
Quadro RTX 5000 X2 Mobile— what is the largest AI model it can run?
The largest model in our catalogue that fits is Nemotron 3-Nano-30B-A3B at 31.6B parameters, compressed to Q3_K_M. It generates roughly 90.0 tokens per second and needs about 14.4 GB of the card's memory.
Quadro RTX 5000 X2 Mobile— how many tokens per second does it produce?
It depends on the model. The fastest model we track here is Gemma 3 QAT 1B at about 190 tokens per second, while larger models run proportionally slower because each token requires reading the whole model out of memory once. Speeds are estimates for a single conversation at a time.
Quadro RTX 5000 X2 Mobile— can it run 7B models?
Yes. For example it runs Gemma 4 E4B at Q8_0, using about 9.8 GB of memory and generating around 42.2 tokens per second.
Quadro RTX 5000 X2 Mobile— can it run 13B models?
Yes. For example it runs DeepSeekMoE-16B at Q6_K, using about 13.7 GB of memory and generating around 95.7 tokens per second.
Quadro RTX 5000 X2 Mobile— can it run 30B models?
Yes. For example it runs ERNIE-4.5-VL-28B-A3B at Q3_K_M, using about 12.9 GB of memory and generating around 102 tokens per second.
Quadro RTX 5000 X2 Mobile— how much memory does it have?
This card has 16 GB of GDDR6. Around a tenth is reserved by the inference runtime and the driver, leaving roughly 14.4 GB available for a model and its conversation.
Quadro RTX 5000 X2 Mobile— what is its memory bandwidth?
Memory bandwidth reaches 448 GB/s across a bus of 256 bits. This is the single best predictor of how fast it generates text, because producing each token means reading the entire model out of memory once.
The other direction
Looking at it from the other side?
This page starts from the hardware. If you already know which model you want and need to know what it takes to run it, start from the model instead.