Calculate the TPS of the Quadro K5200 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
Baichuan 1-13B
13.3B · Q3_K_M · 14.1 tok/s
Fastest model
Gemma 3 QAT 1B
69.2 tok/s · 1B
Which AI models can run on a Quadro K5200?
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.
337 models match
Calculating| Quantisation | Fit | ||||||
|---|---|---|---|---|---|---|---|
|
69.2
tok/s
24–138 · low confidence |
Gemma 3 1B | 1B | Mar 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
69.2
tok/s
24–138 · low confidence |
Gemma 3 QAT 1B | 1B | Apr 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
69.2
tok/s
24–138 · low confidence |
HGRN 1B (WT 103) ≈ | 1B | Nov 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
69.2
tok/s
24–138 · low confidence |
LLama 3..2 Typhoon 2 1B ≈ | 1B | Dec 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
69.2
tok/s
24–138 · low confidence |
OLMo-1B ≈ | 1B | Feb 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
69.2
tok/s
24–138 · low confidence |
Pythia-1b ≈ | 1B | Apr 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
64.1
tok/s
22–128 · low confidence |
OpenELM-1.1B ≈ | 1.1B | May 2024 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
62.9
tok/s
22–126 · low confidence |
DeciCoder-1B ≈ | 1.1B | Aug 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
62.9
tok/s
22–126 · low confidence |
SantaCoder ≈ | 1.1B | Jan 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
62.9
tok/s
22–126 · low confidence |
TinyLlama-1.1B (1T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
62.9
tok/s
22–126 · low confidence |
TinyLlama-1.1B (3T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
57.7
tok/s
20–115 · low confidence |
EXAONE 4.0 (1.2B) ≈ | 1.2B | Jul 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
57.7
tok/s
20–115 · low confidence |
MinerU2.5 ≈ | 1.2B | Sep 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
57.7
tok/s
20–115 · low confidence |
Pleias 1.0 1.2B ≈ | 1.2B | Dec 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
57.7
tok/s
20–115 · low confidence |
Pleias-RAG-1B ≈ | 1.2B | Apr 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
56.3
tok/s
20–113 · low confidence |
Llama 3.2 1B | 1.2B | Sep 2024 | 2.2 GB | 131k tokens | Q8_0 | Comfortable |
|
55.5
tok/s
19–111 · low confidence |
MiniCPM-1.2B ≈ | 1.2B | Jun 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
DeepSeek Coder 1.3B ≈ | 1.3B | Jan 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
DeepSeek-VL-1.3B ≈ | 1.3B | Mar 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
DigiRL ≈ | 1.3B | Jun 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
GLA Transformer 1.3B ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
Janus 1.3B ≈ | 1.3B | Oct 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
Kosmos-2.5 ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
Otter ≈ | 1.3B | May 2023 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
53.3
tok/s
19–107 · low confidence |
Phi-1 ≈ | 1.3B | Oct 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 K5200 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
- 8 GB
- Memory bandwidth
- 192 GB/s
- Memory type
- GDDR5
- Memory bus width
- 256 bit
- Memory clock
- 1.5 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
- GK110B
- Architecture
- Kepler
- Generation
- Quadro Kepler(Kx200)
- Foundry
- TSMC
- Process size
- 28 nm
- Transistors
- 7.1 billion
- Transistor density
- 12,600 K/mm²
- Die size
- 561 mm²
- Package
- BGA-2152
- Released
- 22 July 2014
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
- 667 MHz
- Boost clock
- 771 MHz
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
- 2,304
- Texture mapping units
- 192
- Render output units
- 48
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.
- Single precision (FP32)
- 3.6 TFLOPS
- Double precision (FP64)
- 148 GFLOPS
- Pixel rate
- 37 GPixel/s
- Texture rate
- 148 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)
- 150 W
- Suggested power supply
- 450 W
- Power connectors
- 1x 6-pin
- Bus interface
- PCIe 3.0 x16
- Slot width
- Dual-slot
- Dimensions
- 267 mm
- Display outputs
- 2x DVI, 2x DisplayPort 1.2
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
- 3.5
- DirectX
- 11.1
- OpenGL
- 4.6
- Vulkan
- 1.2
- OpenCL
- 3.0
- Shader model
- 5.1
Listings
Where to buy a Quadro K5200
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
8 GB
Bandwidth
192 GB/s
Largest model
Baichuan 1-13B
At 8 GB of GDDR5 the Quadro K5200 is limited to the smaller end of the catalogue. About 7.2 GB is actually available to a runtime, and a model has to fit entirely inside it before generating anything at all.
At 192 GB/s across a 256-bit bus, bandwidth is this card's real constraint. Every token requires reading the entire model out of memory, so a large model will feel slow here even when it fits.
That comes from a 1.5 GHz memory clock across the bus width above. Widening the bus and raising the clock are the two levers a manufacturer has, which is why a card with unremarkable cores can still generate quickly.
The biggest thing it holds is Baichuan 1-13B (13.3B) at Q3_K_M compression, for about 14.1 tokens per second.
The chip and how it was built
The Quadro K5200 is built on the GK110B graphics processor, using NVIDIA's Kepler architecture, as part of the Quadro Kepler(Kx200) generation.
The chip is manufactured by TSMC, on a 28 nm process, with a die measuring 561 mm², holding 7.1 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 July 2014, roughly 12 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
FP64
148 GFLOPS
Double-precision throughput is 148 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 667 MHz at base to 771 MHz 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
There are 2,304 shading units, 192 texture mapping units, and 48 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
150 W
The Quadro K5200 is rated at 150 W, with a 450 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. 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 K5200
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 K5200
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 K5200
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
The table lists 337 models this Quadro K5200 can run. Search by name, or by size — typing 27b matches on the parameter count even when the name never states it.
-
02
Match the context to your work
Drag the slider to the conversation length you plan to work at. The cache grows with the conversation, and on 8 GB it is often what pushes a large model over the edge.
-
03
Set a minimum quality if you need one
By default the table picks the least-compressed copy that fits. Setting a floor removes models that only qualify through heavy compression.
-
04
Take the range as the answer
The figures are calculated, not measured. 69.2 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 memory column before committing
A tight fit runs but leaves no room to raise the context later; comfortable has headroom. The memory column shows what each model needs against the 8 GB available.
-
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 where the Quadro K5200 sits against the alternatives.
Answers
Quadro K5200 — common questions
Can a Quadro K5200 run a 13B model?
Yes. For example a Quadro K5200 runs Gemma 4 12B at Q3_K_M, using about 6.5 GB of memory and generating around 15.6 tokens per second.
How much memory does a Quadro K5200 have?
A Quadro K5200 has 8 GB of GDDR5 memory. Around a tenth of that is reserved by the inference runtime and the driver, leaving roughly 7.2 GB available for a model and its conversation.
What is the memory bandwidth of a Quadro K5200?
The Quadro K5200 has 192 GB/s of memory bandwidth, across a 256-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 Quadro K5200 use?
It uses GDDR5 clocked at 1.5 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 Quadro K5200?
The Quadro K5200 is a NVIDIA product, with the chip manufactured by TSMC, on a 28 nm process.
When was the Quadro K5200 released?
The Quadro K5200 was released in July 2014.
How much power does a Quadro K5200 use?
The Quadro K5200 has a rated board power of 150 W, and a 450 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.
Does the Quadro K5200 support CUDA?
Yes. The Quadro K5200 reports CUDA compute capability 3.5, 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 Quadro K5200 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 Quadro K5200 good for running local AI models?
Its memory limits it to smaller models though its bandwidth means generation will feel slow on larger models. In total it runs 337 of the models we track. Whether that is enough depends entirely on which model you want — the table above answers that directly.
Can a Quadro K5200 run a model that does not fit in its memory?
Only partly. Layers beyond the 8 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 Quadro K5200 cards be twice as fast?
Capacity adds, throughput does not. Two of them give you 16 GB to work with rather than twice the tokens per second — every figure here is for a single Quadro K5200.
What AI models can a Quadro K5200 run?
337 of the 679 open-weight language models we track fit on a Quadro K5200 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 Quadro K5200 can run?
The largest model in our catalogue that fits on a Quadro K5200 is Baichuan 1-13B at 13.3B parameters, compressed to Q3_K_M. It generates roughly 14.1 tokens per second and needs about 7.2 GB of the card's memory.
How many tokens per second does a Quadro K5200 produce?
It depends on the model. On a Quadro K5200 the fastest model we track is Gemma 3 QAT 1B at about 69.2 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 Quadro K5200 run a 7B model?
Yes. For example a Quadro K5200 runs MetaMath 7B (LLaMa finetune) at Q4_K_M, using about 6.5 GB of memory and generating around 22.8 tokens per second.
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.