Calculate the TPS of the TITAN X Pascal 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
679 models in our catalogue altogether
Largest model it holds
ERNIE-4.5-21B-A3B
21B · Q3_K_M · 123 tok/s
Fastest model
Gemma 3 QAT 1B
173 tok/s · 1B
Which AI models can run on a TITAN X Pascal?
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.
396 models match
Calculating| Quantisation | Fit | ||||||
|---|---|---|---|---|---|---|---|
|
173
tok/s
61–346 · low confidence |
Gemma 3 1B | 1B | Mar 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
173
tok/s
61–346 · low confidence |
Gemma 3 QAT 1B | 1B | Apr 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
173
tok/s
61–346 · low confidence |
HGRN 1B (WT 103) ≈ | 1B | Nov 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
173
tok/s
61–346 · low confidence |
LLama 3..2 Typhoon 2 1B ≈ | 1B | Dec 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
173
tok/s
61–346 · low confidence |
OLMo-1B ≈ | 1B | Feb 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
173
tok/s
61–346 · low confidence |
Pythia-1b ≈ | 1B | Apr 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
160
tok/s
56–320 · low confidence |
OpenELM-1.1B ≈ | 1.1B | May 2024 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
157
tok/s
55–314 · low confidence |
DeciCoder-1B ≈ | 1.1B | Aug 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
157
tok/s
55–314 · low confidence |
SantaCoder ≈ | 1.1B | Jan 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
157
tok/s
55–314 · low confidence |
TinyLlama-1.1B (1T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
157
tok/s
55–314 · low confidence |
TinyLlama-1.1B (3T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
144
tok/s
50–288 · low confidence |
EXAONE 4.0 (1.2B) ≈ | 1.2B | Jul 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
144
tok/s
50–288 · low confidence |
MinerU2.5 ≈ | 1.2B | Sep 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
144
tok/s
50–288 · low confidence |
Pleias 1.0 1.2B ≈ | 1.2B | Dec 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
144
tok/s
50–288 · low confidence |
Pleias-RAG-1B ≈ | 1.2B | Apr 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
141
tok/s
49–281 · low confidence |
Llama 3.2 1B | 1.2B | Sep 2024 | 2.2 GB | 131k tokens | Q8_0 | Comfortable |
|
139
tok/s
49–277 · low confidence |
MiniCPM-1.2B ≈ | 1.2B | Jun 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
139
tok/s
49–277 · low confidence |
DeepSeekMoE-16B | 16B | Jan 2024 | 10.0 GB | 4k tokens | Q4_K_M | Tight |
|
133
tok/s
47–266 · low confidence |
DeepSeek Coder 1.3B ≈ | 1.3B | Jan 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
133
tok/s
47–266 · low confidence |
DeepSeek-VL-1.3B ≈ | 1.3B | Mar 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
133
tok/s
47–266 · low confidence |
DigiRL ≈ | 1.3B | Jun 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
133
tok/s
47–266 · low confidence |
GLA Transformer 1.3B ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
133
tok/s
47–266 · low confidence |
Janus 1.3B ≈ | 1.3B | Oct 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
133
tok/s
47–266 · low confidence |
Kosmos-2.5 ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
133
tok/s
47–266 · 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
TITAN X Pascal 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
- 12 GB
- Memory bandwidth
- 480 GB/s
- Memory type
- GDDR5X
- Memory bus width
- 384 bit
- Memory clock
- 1.25 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
- GP102
- Architecture
- Pascal
- Generation
- GeForce 10
- Foundry
- TSMC
- Process size
- 16 nm
- Transistors
- 11.8 billion
- Transistor density
- 25,100 K/mm²
- Die size
- 471 mm²
- Package
- BGA-2397
- Released
- 2 August 2016
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.42 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,584
- Texture mapping units
- 224
- Render output units
- 96
- Streaming multiprocessors
- 28
- L1 cache
- 48 KB
- L2 cache
- 3 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)
- 171.5 GFLOPS
- Single precision (FP32)
- 11 TFLOPS
- Double precision (FP64)
- 342.9 GFLOPS
- Pixel rate
- 147 GPixel/s
- Texture rate
- 343 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)
- 250 W
- Suggested power supply
- 600 W
- Power connectors
- 1x 6-pin + 1x 8-pin
- Bus interface
- PCIe 3.0 x16
- Slot width
- Dual-slot
- Dimensions
- 267 mm × 40 mm
- Display outputs
- 1x DVI, 1x HDMI 2.0, 3x DisplayPort 1.4a
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
- 6.1
- DirectX
- 12.1
- OpenGL
- 4.6
- Vulkan
- 1.4
- OpenCL
- 3.0
- Shader model
- 6.8
Listings
Where to buy a TITAN X Pascal
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
Memory: the specification that decides everything
Memory
12 GB
Bandwidth
480 GB/s
Largest model
ERNIE-4.5-21B-A3B
12 GB of GDDR5X puts the TITAN X Pascal comfortably into small and mid-sized models, with roughly 10.8 GB usable once the driver overhead is taken out. The largest models are out of reach without splitting them.
The memory bus moves 480 GB/s across a 384-bit bus. That is the number that governs generation speed — arithmetic per byte read is small enough that the bus, not the cores, is what everything waits on.
The figure is the memory clock — 1.25 GHz here — multiplied by the bus width. It is why core counts predict generation speed so poorly.
The practical ceiling is ERNIE-4.5-21B-A3B at 21B, held at Q3_K_M and running at roughly 123 tokens per second.
The chip and how it was built
The TITAN X Pascal is built on the GP102 graphics processor, using NVIDIA's Pascal architecture, as part of the GeForce 10 generation.
The chip is manufactured by TSMC, on a 16 nm process, with a die measuring 471 mm², holding 11.8 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 August 2016, roughly 9 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
171.5 GFLOPS
FP64
342.9 GFLOPS
On paper the TITAN X Pascal reaches 171.5 GFLOPS at half precision and 11 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 is 342.9 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.
Clocks run from 1.42 GHz at base to 1.53 GHz boosted. 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
The TITAN X Pascal has 48 KB of L1 cache, backed by 3 MB of L2. 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,584 shading units, 224 texture mapping units, and 96 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
250 W
The TITAN X Pascal is rated at 250 W, with a 600 W power supply suggested for the whole system. 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 a dual-slot, measuring 267 mm long, and needs 1x 6-pin + 1x 8-pin. 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 TITAN X Pascal
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 TITAN X Pascal
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 TITAN X Pascal
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
Find the model in the table
Every one of the 396 models this TITAN X Pascal runs is in the table above. Search narrows it by name or by size.
-
02
Decide how long your conversations run
Set the context to your real working length. Short questions cost almost nothing; a long document can consume a large share of the card's 12 GB.
-
03
Choose how far you will compress
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
Read the speed and the range
The figures are calculated, not measured. 173 tok/s on Gemma 3 QAT 1B is the fastest result on this card, and like every row it carries a range that reflects how much the runtime matters.
-
05
Check the headroom before you decide
The fit column separates models that just fit from those with room to spare — worth checking against the card's 12 GB before settling on one.
-
06
Cross-check against other hardware
Following a model through to its own page lists all the hardware that can run it, so you can see where the TITAN X Pascal sits against the alternatives.
Answers
TITAN X Pascal — common questions
What AI models can a TITAN X Pascal run?
396 of the 679 open-weight language models we track fit on a TITAN X Pascal and can be run locally on it. The table on this page lists every one, with the memory it needs, the quantisation it runs at and an estimated generation speed.
What is the largest AI model a TITAN X Pascal can run?
The largest model in our catalogue that fits on a TITAN X Pascal is ERNIE-4.5-21B-A3B at 21B parameters, compressed to Q3_K_M. It generates roughly 123 tokens per second and needs about 10.1 GB of the card's memory.
How many tokens per second does a TITAN X Pascal produce?
It depends on the model. On a TITAN X Pascal the fastest model we track is Gemma 3 QAT 1B at about 173 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.
Can a TITAN X Pascal run a 7B model?
Yes. For example a TITAN X Pascal runs DeepSeek Coder 6.7B at Q6_K, using about 9.9 GB of memory and generating around 37.5 tokens per second.
Can a TITAN X Pascal run a 13B model?
Yes. For example a TITAN X Pascal runs DeepSeekMoE-16B at Q4_K_M, using about 10.0 GB of memory and generating around 139 tokens per second.
How much memory does a TITAN X Pascal have?
A TITAN X Pascal has 12 GB of GDDR5X memory. Around a tenth of that is reserved by the inference runtime and the driver, leaving roughly 10.8 GB available for a model and its conversation.
What is the memory bandwidth of a TITAN X Pascal?
The TITAN X Pascal has 480 GB/s of memory bandwidth, across a 384-bit memory bus. 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.
What type of memory does a TITAN X Pascal use?
It uses GDDR5X clocked at 1.25 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.
Who makes the TITAN X Pascal?
The TITAN X Pascal is a NVIDIA product, with the chip manufactured by TSMC, on a 16 nm process.
When was the TITAN X Pascal released?
The TITAN X Pascal was released in August 2016.
How much power does a TITAN X Pascal use?
The TITAN X Pascal has a rated board power of 250 W, and a 600 W system power supply is suggested. Generating text draws hard in bursts and idles between requests, so average consumption over a working session is normally well below the rated figure.
How much cache does a TITAN X Pascal have?
The TITAN X Pascal has 48 KB of L1 cache, and 3 MB of L2 cache. 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.
What are the TFLOPS of a TITAN X Pascal?
The TITAN X Pascal is rated at 171.5 GFLOPS at half precision and 11 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.
Does the TITAN X Pascal support CUDA?
Yes. The TITAN X Pascal reports CUDA compute capability 6.1, which predates tensor cores. 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.
What bus interface does the TITAN X Pascal 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.
Is the TITAN X Pascal 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 396 of the models we track. Whether that is enough depends entirely on which model you want — the table above answers that directly.
Can a TITAN X Pascal run a model that does not fit in its memory?
Only partly. Layers beyond the 12 GB 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 it is fully resident on the card.
Would two TITAN X Pascal cards be twice as fast?
No. A second TITAN X Pascal doubles the memory to 24 GB, which lets you hold models neither could hold alone, but generation does not split that way. These figures describe one card.
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.