Calculate the TPS of the DRIVE A100 PROD 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
Largest model it holds
Phi-3.5-MoE
60.8B · Q3_K_M · 195 tok/s
Fastest model
Gemma 3 QAT 1B
792 tok/s · 1B
What AI models can a DRIVE A100 PROD run?
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.
513 models match
Calculating| Quantisation | Fit | ||||||
|---|---|---|---|---|---|---|---|
|
792
tok/s
673–950 |
Gemma 3 1B | 1B | Mar 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
792
tok/s
673–950 |
Gemma 3 QAT 1B | 1B | Apr 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
792
tok/s
475–1,267 · low confidence |
HGRN 1B (WT 103) ≈ | 1B | Nov 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
792
tok/s
475–1,267 · low confidence |
LLama 3..2 Typhoon 2 1B ≈ | 1B | Dec 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
792
tok/s
475–1,267 · low confidence |
OLMo-1B ≈ | 1B | Feb 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
792
tok/s
475–1,267 · low confidence |
Pythia-1b ≈ | 1B | Apr 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
733
tok/s
440–1,173 · low confidence |
OpenELM-1.1B ≈ | 1.1B | May 2024 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
DeciCoder-1B ≈ | 1.1B | Aug 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
SantaCoder ≈ | 1.1B | Jan 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
TinyLlama-1.1B (1T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
720
tok/s
432–1,152 · low confidence |
TinyLlama-1.1B (3T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
660
tok/s
396–1,056 · low confidence |
EXAONE 4.0 (1.2B) ≈ | 1.2B | Jul 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
660
tok/s
396–1,056 · low confidence |
MinerU2.5 ≈ | 1.2B | Sep 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
660
tok/s
396–1,056 · low confidence |
Pleias 1.0 1.2B ≈ | 1.2B | Dec 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
660
tok/s
396–1,056 · low confidence |
Pleias-RAG-1B ≈ | 1.2B | Apr 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
644
tok/s
547–773 |
Llama 3.2 1B | 1.2B | Sep 2024 | 2.2 GB | 131k tokens | Q8_0 | Comfortable |
|
635
tok/s
381–1,016 · low confidence |
MiniCPM-1.2B ≈ | 1.2B | Jun 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · low confidence |
DeepSeek Coder 1.3B ≈ | 1.3B | Jan 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · low confidence |
DeepSeek-VL-1.3B ≈ | 1.3B | Mar 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · low confidence |
DigiRL ≈ | 1.3B | Jun 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · low confidence |
GLA Transformer 1.3B ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · low confidence |
Janus 1.3B ≈ | 1.3B | Oct 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · low confidence |
Kosmos-2.5 ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · low confidence |
Otter ≈ | 1.3B | May 2023 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
609
tok/s
366–975 · 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
DRIVE A100 PROD 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
- 32 GB
- Memory bandwidth
- 1,870 GB/s
- Memory type
- HBM2e
- Memory bus width
- 6,144 bit
- Memory clock
- 1.22 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
- GA100
- Architecture
- Ampere
- Generation
- DRIVE(Axx)
- Foundry
- TSMC
- Process size
- 7 nm
- Transistors
- 54.2 billion
- Transistor density
- 65,600 K/mm²
- Die size
- 826 mm²
- Package
- BGA-2743
- Released
- 14 May 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.26 GHz
- Boost clock
- 1.26 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
- 6,912
- Texture mapping units
- 432
- Render output units
- 192
- Streaming multiprocessors
- 108
- Tensor cores
- 432
- L1 cache
- 192 KB
- L2 cache
- 32 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)
- 69.7 TFLOPS
- Single precision (FP32)
- 17.4 TFLOPS
- Double precision (FP64)
- 8.7 TFLOPS
- Pixel rate
- 242 GPixel/s
- Texture rate
- 544 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)
- 400 W
- Suggested power supply
- 800 W
- Power connectors
- None
- Bus interface
- PCIe 4.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
- 8.0
- OpenCL
- 3.0
Listings
Where to buy a DRIVE A100 PROD
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
32 GB
Bandwidth
1,870 GB/s
Largest model
Phi-3.5-MoE
The DRIVE A100 PROD carries 32 GB of HBM2e, which covers the mid-sized models most people actually run — about 28.8 GB of it after the runtime and driver reserve their working space.
Bandwidth is 1,870 GB/s across a 6,144-bit bus. Generating a token means reading every weight once, so that figure sets the pace more than any other number here, and at this level text arrives faster than most people read.
That comes from a 1.22 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 practical ceiling is Phi-3.5-MoE at 60.8B, held at Q3_K_M and running at roughly 195 tokens per second.
The chip and how it was built
The DRIVE A100 PROD is built on the GA100 graphics processor, using NVIDIA's Ampere architecture, as part of the DRIVE(Axx) generation.
The chip is manufactured by TSMC, on a 7 nm process, with a die measuring 826 mm², holding 54.2 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 May 2020, roughly 6 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
69.7 TFLOPS
FP64
8.7 TFLOPS
Tensor cores
432
On paper the DRIVE A100 PROD reaches 69.7 TFLOPS at half precision and 17.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 is 8.7 TFLOPS. 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 432 tensor cores across 108 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 1.26 GHz at base to 1.26 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 DRIVE A100 PROD has 192 KB of L1 cache, backed by 32 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 6,912 shading units, 432 texture mapping units, and 192 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
400 W
The DRIVE A100 PROD is rated at 400 W, with a 800 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 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 4.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 a DRIVE A100 PROD can run
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 DRIVE A100 PROD
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 DRIVE A100 PROD
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 513 models this DRIVE A100 PROD can run. Search by name, or by size — typing 27b matches on the parameter count even when the name never states it.
-
02
Decide how long your conversations run
Drag the slider to the conversation length you plan to work at. The cache grows with the conversation, and on 32 GB it is often what pushes a large model over the edge.
-
03
Choose how far you will compress
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. 792 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 32 GB before settling on one.
-
06
Check the same model from the other side
Following a model through to its own page lists all the hardware that can run it, so you can see where the DRIVE A100 PROD sits against the alternatives.
Answers
DRIVE A100 PROD — common questions
How many tokens per second does a DRIVE A100 PROD produce?
It depends on the model. On a DRIVE A100 PROD the fastest model we track is Gemma 3 QAT 1B at about 792 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 DRIVE A100 PROD run a 7B model?
Yes. For example a DRIVE A100 PROD runs Multi-Token Prediction 7B at Q8_0, using about 7.9 GB of memory and generating around 118 tokens per second.
Can a DRIVE A100 PROD run a 13B model?
Yes. For example a DRIVE A100 PROD runs DeepSeekMoE-16B at Q8_0, using about 17.5 GB of memory and generating around 275 tokens per second.
Can a DRIVE A100 PROD run a 30B model?
Yes. For example a DRIVE A100 PROD runs ERNIE-4.5-VL-28B-A3B at Q6_K, using about 22.7 GB of memory and generating around 228 tokens per second.
How much memory does a DRIVE A100 PROD have?
A DRIVE A100 PROD has 32 GB of HBM2e memory. Around a tenth of that is reserved by the inference runtime and the driver, leaving roughly 28.8 GB available for a model and its conversation.
What is the memory bandwidth of a DRIVE A100 PROD?
The DRIVE A100 PROD has 1,870 GB/s of memory bandwidth, across a 6,144-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 DRIVE A100 PROD use?
It uses HBM2e clocked at 1.22 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 DRIVE A100 PROD?
The DRIVE A100 PROD is a NVIDIA product, with the chip manufactured by TSMC, on a 7 nm process.
When was the DRIVE A100 PROD released?
The DRIVE A100 PROD was released in May 2020.
How much power does a DRIVE A100 PROD use?
The DRIVE A100 PROD has a rated board power of 400 W, and a 800 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 DRIVE A100 PROD have?
The DRIVE A100 PROD has 192 KB of L1 cache, and 32 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 DRIVE A100 PROD?
The DRIVE A100 PROD is rated at 69.7 TFLOPS at half precision and 17.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.
How many tensor cores does a DRIVE A100 PROD have?
The DRIVE A100 PROD has 432 tensor cores across 108 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.
Does the DRIVE A100 PROD support CUDA?
Yes. The DRIVE A100 PROD reports CUDA compute capability 8.0. 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 DRIVE A100 PROD use?
It uses PCIe 4.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 DRIVE A100 PROD good for running local AI models?
Its memory comfortably covers the mid-sized models most people run locally and its bandwidth is high enough to generate text faster than most people read. In total it runs 513 of the models we track. Whether that is enough depends entirely on which model you want — the table above answers that directly.
Can a DRIVE A100 PROD run a model that does not fit in its memory?
Only partly. Layers beyond the 32 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 DRIVE A100 PROD cards be twice as fast?
Pairing DRIVE A100 PROD cards buys headroom rather than pace: 64 GB of combined memory, at roughly the same generation speed as one.
What AI models can a DRIVE A100 PROD run?
513 of the 679 open-weight language models we track fit on a DRIVE A100 PROD 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 DRIVE A100 PROD can run?
The largest model in our catalogue that fits on a DRIVE A100 PROD is Phi-3.5-MoE at 60.8B parameters, compressed to Q3_K_M. It generates roughly 195 tokens per second and needs about 27.2 GB of the card's memory.
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.