AI chip · Google
Google TPU v5e
Cost-efficient TPU generation optimized for inference and smaller training runs; the mainstream Google Cloud TPU offering.
Deployed in 1 named data center.
Market position
Fifth-generation inference-optimised TPU. Cheaper per-chip than v5p, positioned against NVIDIA L4 for cost-sensitive inference on Google Cloud. Superseded by v6e for new deployments.
Efficiency and power
How much work you get per watt and per dollar, and how much power a full rack draws.
- Perf per watt
- 1.16 BF16 TFLOPS/W197 TFLOPS ÷ 170 W = 1.16
What fits in 16 GB
Which open-source LLMs run on one Google TPU v5e, by precision. Weights only: add roughly 15% headroom for real serving. If a model does not fit at FP16, try INT8 or INT4 (smaller quality trade-off than most people expect).
| Model | Params | FP16 | INT8 | INT4 |
|---|---|---|---|---|
| Llama 3.1 8B dense | 8 B | 16 GB ✓ | 8 GB ✓ | 4 GB ✓ |
| Llama 3.1 70B dense | 70 B | 140 GB ✗ | 70 GB ✗ | 35 GB ✗ |
| Llama 3.1 405B dense | 405 B | 810 GB ✗ | 405 GB ✗ | 203 GB ✗ |
| Llama 3.3 70B dense | 70 B | 140 GB ✗ | 70 GB ✗ | 35 GB ✗ |
| DeepSeek V3 MoE (671B total, 37B active per token) | 671 B | 1342 GB ✗ | 671 GB ✗ | 336 GB ✗ |
| DeepSeek R1 MoE (671B total, 37B active per token) | 671 B | 1342 GB ✗ | 671 GB ✗ | 336 GB ✗ |
| Qwen 2.5 7B dense | 7 B | 14 GB ✓ | 7 GB ✓ | 4 GB ✓ |
| Qwen 2.5 72B dense | 72 B | 144 GB ✗ | 72 GB ✗ | 36 GB ✗ |
| Mixtral 8x7B MoE (46.7B total, 12.9B active per token) | 46.7 B | 93 GB ✗ | 47 GB ✗ | 23 GB ✗ |
| Mixtral 8x22B MoE (141B total, 39B active per token) | 141 B | 282 GB ✗ | 141 GB ✗ | 71 GB ✗ |
| Gemma 2 27B dense | 27 B | 54 GB ✗ | 27 GB ✗ | 14 GB ✓ |
| Command R+ dense | 104 B | 208 GB ✗ | 104 GB ✗ | 52 GB ✗ |
| Kimi K2 MoE (1T total, 32B active per token) | 1000 B | 2000 GB ✗ | 1000 GB ✗ | 500 GB ✗ |
Math: FP16 = params × 2 bytes; INT8 = params × 1 byte; INT4 = params × 0.5 bytes. MoE models sum every expert (full weights on disk), not the per-token active subset.
Common questions
How much does Google TPU v5e cost?
Google TPU v5e doesn't have a public launch list price. Vendors like this one usually price through direct sales rather than a public sheet. See list price per TFLOP for chips that do publish.
How much memory does Google TPU v5e have?
16 GB of HBM2, running at 819 GB/s. Straight from the vendor datasheet. See chips with the most memory for context.
How much power does one Google TPU v5e draw?
170 W at the chip. A full server draws more once you add CPU, memory, networking and cooling: see the rack power number above. Compare to other chips on perf-per-watt.
Which data centers use Google TPU v5e?
1 named data center runs them, including Google Dorchester & Berkeley County. See who has the most Google TPU v5e for the ranked list.
Which open-source LLMs fit on one Google TPU v5e?
Of 13 open-source LLMs we track, 2 fit at FP16, 2 at INT8, and 3 at INT4 (for example Llama 3.1 8B, Qwen 2.5 7B and Gemma 2 27B). Full table above with each model's memory need.
Key facts
- Class
- Compute SoC (AI accelerator)
- Designer
- Safety-critical?
- No (data-center inference / training)
- Record as of
- 2026-09-27
- Most recent source
- 2024-01-01 (across 1 source on this page)
Specifications (8 fields, click to expand)
Straight from the vendor datasheet. Dense throughput shown first; sparse (2:4) numbers in parentheses where the vendor publishes them. Full datasheet linked below.
- TDP
- 170 W
- Memory
- 16 GB HBM2
- Memory bandwidth
- 819 GB/s
- BF16 (dense)
- 197 TFLOPS
- INT8 (dense)
- 393 TOPS
- Form factor
- OAM (v5e pod, up to 256 chips)
- Announced
- 2023-08-29
- Released
- 2023-11-01
Source: vendor datasheet
Generation
Foundry & process
- Fabbed at
- TSMC (all chips TSMC makes →)
Compare with
Data centers running Google TPU v5e
Who has the most? →Named data-center campuses with Google TPU v5e on site. Counts shown where the operator has published them; other rows are described in general terms.
- Google Dorchester & Berkeley County Data Center Campusesas of 2024-01-01under constructionreported
us-east4-adjacent TPU v5e capacity
Sources
- Cloud TPU v5eGoogle Cloud
Adoption rows appear as we confirm each chip-in-robot pairing from a public source. See every chip we track for the full catalog or the Google page.