Calculate the TPS of the GRID A100A 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
Phi-3.5-MoE
60.8B · Q3_K_M · 195 tok/s
Fastest model
Gemma 3 QAT 1B
792 tok/s · 1B
Which AI models can run on a GRID A100A?
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.
543 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 |
LFM2-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 |
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
GRID A100A 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
- GRID(Ax)
- 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.1 GHz
- Boost clock
- 1.41 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)
- 78 TFLOPS
- Single precision (FP32)
- 19.5 TFLOPS
- Double precision (FP64)
- 9.7 TFLOPS
- Pixel rate
- 271 GPixel/s
- Texture rate
- 609 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 GRID A100A
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
What the memory subsystem means for AI
Memory
32 GB
Bandwidth
1,870 GB/s
Largest model
Phi-3.5-MoE
GRID A100A carries 32 GB of HBM2e. That covers the mid-sized models most people actually run. Once the runtime and driver reserve their working space, roughly this much is left: 28.8 GB.
Memory bandwidth reaches 1,870 GB/s across a bus of 6,144 bits. 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 memory clock of 1.22 GHz. Both halves matter, and neither is visible in a gaming benchmark.
Put together, the largest model that fits is Phi-3.5-MoE, 60.8B, compressed to Q3_K_M and generating around 195 tokens per second.
The chip and how it was built
GRID A100A is built on the graphics processor GA100, using the architecture Ampere from NVIDIA, as part of the generation GRID(Ax).
The chip is manufactured by TSMC, on a process of 7 nm, 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.3357883501626 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
78 TFLOPS
FP64
9.7 TFLOPS
Tensor cores
432
On paper GRID A100A reaches 78 TFLOPS at half precision, and 19.5 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 9.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 a base of 1.1 GHz to a boost of 1.41 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
GRID A100A has an L1 cache of 192 KB, backed by an L2 cache of 32 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 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
GRID A100A is rated at 400 W, and the suggested system power supply is 800 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 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 that run on a GRID A100A
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 GRID A100A
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 GRID A100A
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 543 models this card runs. Search narrows the list by name or by size.
-
02
Set the context length you will actually use
Set the context to your real working length. Short questions cost almost nothing, but a long document can consume a large share of 32 GB so the setting is worth getting right.
-
03
Set a minimum quality if you need one
Compression is what lets bigger models fit. The quality control drops any model that needs more of it than you are willing to give.
-
04
Take the range as the answer
Speeds come with error bars for a reason. The best case here is 792 tok/s on Gemma 3 QAT 1B. The same card and model vary by thirty to fifty per cent between inference runtimes.
-
05
Check the headroom before you decide
Tight means it works today; comfortable means it still works when the conversation grows. Compare what each model needs against an available 32 GB.
-
06
Cross-check against other hardware
Each model page repeats this calculation for the whole catalogue. Worth a look before deciding: it shows what else runs the same model, alongside GRID A100A.
Answers
GRID A100A — common questions
GRID A100A— can it run 30B models?
Yes. For example it runs ERNIE-4.5-VL-28B-A3B at Q6_K, using about 22.7 GB of memory and generating around 228 tokens per second.
GRID A100A— how much memory does it have?
This card has 32 GB of HBM2e. Around a tenth is reserved by the inference runtime and the driver, leaving roughly 28.8 GB available for a model and its conversation.
GRID A100A— what is its memory bandwidth?
Memory bandwidth reaches 1,870 GB/s across a bus of 6,144 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.
GRID A100A— what type of memory does it 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.
GRID A100A— who makes it?
This is a product of NVIDIA, with the chip manufactured by TSMC, on a process of 7 nm.
GRID A100A— when was it released?
It was released in May 2020.
GRID A100A— how much power does it use?
Rated board power is 400 W, and the suggested system power supply is 800 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.
GRID A100A— how much cache does it have?
The L1 cache is 192 KB, and the L2 cache is 32 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.
GRID A100A— what are its TFLOPS?
It is rated at 78 TFLOPS at half precision and 19.5 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.
GRID A100A— how many tensor cores does it have?
It 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.
GRID A100A— does it support CUDA?
Yes. It 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.
GRID A100A— what bus interface does it 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.
GRID A100A— is it 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 543 of the models we track. Whether that is enough depends entirely on which model you want — the table above answers that directly.
GRID A100A— can it run a model that does not fit in its memory?
Offloading past the card's 32 GB drags the whole thing down, and none of the figures on this page assume it.
Would two GRID A100A cards be twice as fast?
Pairing them buys headroom rather than pace: 64 GB of combined memory, at roughly the same generation speed as one.
GRID A100A— which AI models can it run?
543 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.
GRID A100A— what is the largest AI model it can run?
The largest model in our catalogue that fits 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.
GRID A100A— 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 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.
GRID A100A— 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 176 tokens per second.
GRID A100A— can it run 13B models?
Yes. For example it runs DeepSeekMoE-16B at Q8_0, using about 17.5 GB of memory and generating around 275 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.