Calculate the TPS of the T400 4 GB 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
DeciLM 6B
5.7B · Q3_K_M · 16.0 tok/s
Fastest model
Gemma 3 QAT 1B
33.9 tok/s · 1B
Which AI models can run on a T400 4 GB?
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.
97 models match
Calculating| Quantisation | Fit | ||||||
|---|---|---|---|---|---|---|---|
|
33.9
tok/s
29–41 |
Gemma 3 1B | 1B | Mar 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
33.9
tok/s
29–41 |
Gemma 3 QAT 1B | 1B | Apr 2025 | 1.8 GB | 33k tokens | Q8_0 | Comfortable |
|
33.9
tok/s
20–54 · low confidence |
HGRN 1B (WT 103) ≈ | 1B | Nov 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
33.9
tok/s
20–54 · low confidence |
LLama 3..2 Typhoon 2 1B ≈ | 1B | Dec 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
33.9
tok/s
20–54 · low confidence |
OLMo-1B ≈ | 1B | Feb 2024 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
33.9
tok/s
20–54 · low confidence |
Pythia-1b ≈ | 1B | Apr 2023 | 1.8 GB | 131k tokens ? | Q8_0 | Comfortable |
|
31.4
tok/s
19–50 · low confidence |
OpenELM-1.1B ≈ | 1.1B | May 2024 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
30.8
tok/s
18–49 · low confidence |
DeciCoder-1B ≈ | 1.1B | Aug 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
30.8
tok/s
18–49 · low confidence |
SantaCoder ≈ | 1.1B | Jan 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
30.8
tok/s
18–49 · low confidence |
TinyLlama-1.1B (1T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
30.8
tok/s
18–49 · low confidence |
TinyLlama-1.1B (3T token checkpoint) ≈ | 1.1B | Oct 2023 | 1.9 GB | 131k tokens ? | Q8_0 | Comfortable |
|
28.2
tok/s
17–45 · low confidence |
EXAONE 4.0 (1.2B) ≈ | 1.2B | Jul 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
28.2
tok/s
17–45 · low confidence |
MinerU2.5 ≈ | 1.2B | Sep 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
28.2
tok/s
17–45 · low confidence |
Pleias 1.0 1.2B ≈ | 1.2B | Dec 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
28.2
tok/s
17–45 · low confidence |
Pleias-RAG-1B ≈ | 1.2B | Apr 2025 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
27.6
tok/s
23–33 |
Llama 3.2 1B | 1.2B | Sep 2024 | 2.2 GB | 54k tokens | Q8_0 | Comfortable |
|
27.2
tok/s
16–43 · low confidence |
MiniCPM-1.2B ≈ | 1.2B | Jun 2024 | 2.0 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · low confidence |
DeepSeek Coder 1.3B ≈ | 1.3B | Jan 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · low confidence |
DeepSeek-VL-1.3B ≈ | 1.3B | Mar 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · low confidence |
DigiRL ≈ | 1.3B | Jun 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · low confidence |
GLA Transformer 1.3B ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · low confidence |
Janus 1.3B ≈ | 1.3B | Oct 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · low confidence |
Kosmos-2.5 ≈ | 1.3B | Aug 2024 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · low confidence |
Otter ≈ | 1.3B | May 2023 | 2.1 GB | 131k tokens ? | Q8_0 | Comfortable |
|
26.1
tok/s
16–42 · 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
T400 4 GB 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
- 4 GB
- Memory bandwidth
- 80 GB/s
- Memory type
- GDDR6
- Memory bus width
- 64 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
- TU117
- Architecture
- Turing
- Generation
- Quadro Turing(Tx000)
- Foundry
- TSMC
- Process size
- 12 nm
- Transistors
- 4.7 billion
- Transistor density
- 23,500 K/mm²
- Die size
- 200 mm²
- Package
- BGA-960
- Released
- 6 May 2021
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
- 420 MHz
- Boost clock
- 1.43 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
- 384
- Texture mapping units
- 24
- Render output units
- 16
- Streaming multiprocessors
- 6
- L1 cache
- 64 KB
- L2 cache
- 1 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)
- 2.2 TFLOPS
- Single precision (FP32)
- 1.1 TFLOPS
- Double precision (FP64)
- 34.2 GFLOPS
- Pixel rate
- 23 GPixel/s
- Texture rate
- 34 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)
- 30 W
- Suggested power supply
- 200 W
- Power connectors
- None
- Bus interface
- PCIe 3.0 x16
- Slot width
- Single-slot
- Display outputs
- 3x mini-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
- 7.5
- DirectX
- 12.1
- OpenGL
- 4.6
- Vulkan
- 1.4
- OpenCL
- 3.0
- Shader model
- 6.8
Listings
Where to buy a T400 4 GB
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
4 GB
Bandwidth
80 GB/s
Largest model
DeciLM 6B
At 4 GB of GDDR6 the T400 4 GB is limited to the smaller end of the catalogue. About 3.6 GB is actually available to a runtime, and a model has to fit entirely inside it before generating anything at all.
At 80 GB/s across a 64-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.25 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.
In practice that combination tops out at DeciLM 6B — 5.7B, compressed to Q3_K_M, generating around 16.0 tokens per second.
The chip and how it was built
The T400 4 GB is built on the TU117 graphics processor, using NVIDIA's Turing architecture, as part of the Quadro Turing(Tx000) generation.
The chip is manufactured by TSMC, on a 12 nm process, with a die measuring 200 mm², holding 4.7 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 2021, roughly 5 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
2.2 TFLOPS
FP64
34.2 GFLOPS
On paper the T400 4 GB reaches 2.2 TFLOPS at half precision and 1.1 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 34.2 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 420 MHz at base to 1.43 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 T400 4 GB has 64 KB of L1 cache, backed by 1 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 384 shading units, 24 texture mapping units, and 16 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
30 W
The T400 4 GB is rated at 30 W, with a 200 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 single-slot. 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 T400 4 GB
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 T400 4 GB
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 T400 4 GB
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
Search for the model you want
Every one of the 97 models this T400 4 GB runs is in the table above. Search narrows it by name or by size.
-
02
Match the context to your work
Longer conversations cost memory on top of the weights. With 4 GB to work in, that is frequently the difference between a model fitting and not.
-
03
Set a minimum quality if you need one
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
The figures are calculated, not measured. 33.9 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
Compare what each model needs with the 4 GB this card provides. Tight means it works today; comfortable means it still works when the conversation grows.
-
06
Check the same model from the other side
Every model name in the table links to its own page, which runs the same calculation across every card we hold. That is where you see whether the T400 4 GB is the right buy for it or merely a card that fits.
Answers
T400 4 GB — common questions
How many tokens per second does a T400 4 GB produce?
It depends on the model. On a T400 4 GB the fastest model we track is Gemma 3 QAT 1B at about 33.9 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.
How much memory does a T400 4 GB have?
A T400 4 GB has 4 GB of GDDR6 memory. Around a tenth of that is reserved by the inference runtime and the driver, leaving roughly 3.6 GB available for a model and its conversation.
What is the memory bandwidth of a T400 4 GB?
The T400 4 GB has 80 GB/s of memory bandwidth, across a 64-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 T400 4 GB use?
It uses GDDR6 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 T400 4 GB?
The T400 4 GB is a NVIDIA product, with the chip manufactured by TSMC, on a 12 nm process.
When was the T400 4 GB released?
The T400 4 GB was released in May 2021.
How much power does a T400 4 GB use?
The T400 4 GB has a rated board power of 30 W, and a 200 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 T400 4 GB have?
The T400 4 GB has 64 KB of L1 cache, and 1 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 T400 4 GB?
The T400 4 GB is rated at 2.2 TFLOPS at half precision and 1.1 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 T400 4 GB support CUDA?
Yes. The T400 4 GB 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.
What bus interface does the T400 4 GB 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 T400 4 GB 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 97 of the models we track. Whether that is enough depends entirely on which model you want — the table above answers that directly.
Can a T400 4 GB run a model that does not fit in its memory?
It can be split, with the overflow held in system memory — but that part drags the whole thing down, and none of the 4 GB figures on this page assume it.
Would two T400 4 GB cards be twice as fast?
Pairing T400 4 GB cards buys headroom rather than pace: 8 GB of combined memory, at roughly the same generation speed as one.
What AI models can a T400 4 GB run?
97 of the 679 open-weight language models we track fit on a T400 4 GB 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 T400 4 GB can run?
The largest model in our catalogue that fits on a T400 4 GB is DeciLM 6B at 5.7B parameters, compressed to Q3_K_M. It generates roughly 16.0 tokens per second and needs about 3.5 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.