Skip to main content

TPU hardware versions

Exam guide§2.1

Tensor Processing Units are Google's custom accelerators for the compute-heavy math of machine learning. This page walks the Cloud TPU family from the newest generation back to the foundational one - what distinguishes each version and how to choose the right accelerator for a demanding AI workload.

Cloud TPU family: a quick overview

Google TPU evolution timeline from V1 (2015) to Ironwood (2025), with per-chip and per-pod performance multipliers
Google TPU evolution - each generation adds compute per chip and scale per pod, from the internal V1 inference chip (2015) to Ironwood (2025), the largest pod.
VersionWhat defines it
TPU v2The foundational public Cloud TPU - introduced scalable TPU slices with a 2D torus interconnect.
TPU v3A step up from v2 - more compute per TensorCore and greater memory, for larger models that didn't fit on v2.
TPU v4Flexible and efficient - 3D mesh topology, improved memory system, advanced options like twisted tori.
TPU v5pPowerful and scalable - large-scale 3D interconnect topology and high HBM capacity, for very large models.
TPU v6e (Trillium)Highest value and performance for transformer, text-to-image, and CNN models; adds SparseCore for embeddings.
TPU v7e (Ironwood)Builds on Trillium and optimizes custom AI accelerators primarily for inference workloads.

Ironwood (v7e): inference acceleration

Ironwood is designed to be highly performant, scalable, and energy-efficient, reflecting a strategic shift toward accelerating inference at scale. That focus supports the move from reactive AI systems (which surface data for humans to interpret) to proactive AI agents that autonomously retrieve, generate, and interpret data. Ironwood is purpose-built for the computational and communication demands of this "age of inference" - large language models, Mixture of Experts (MoEs), and reasoning tasks - minimizing on-chip data movement and latency while running extensive tensor manipulations.

NumbersIronwood per-chip performance
  • Peak compute per chip - 4,614 TFLOPs (TeraFLOPs).
  • HBM capacity per chip - 192 GB of High Bandwidth Memory.
  • HBM bandwidth per chip - 7.37 TB/s.
  • Inter-Chip Interconnect (ICI) bandwidth - 1.2 TBps bidirectional, for coordinated, synchronous communication across the full pod.
NumbersIronwood scale and power efficiency
  • Pod scale - up to 9,216 liquid-cooled chips.
  • Aggregate compute - a 9,216-chip pod delivers 42.5 exaflops.
  • Power efficiency - 2x performance per watt vs. Trillium, and ~30x more power efficient than the first Cloud TPU (v2, 2018), supported by advanced liquid cooling.
Seven-rack Ironwood TPU unit with a liquid-cooling unit on the far right
A seven-rack Ironwood TPU unit - the liquid-cooling unit sits on the far right.

Trillium (v6e)

Trillium (v6e) is Cloud TPU's newest-generation accelerator before Ironwood. Each Trillium chip contains a single TensorCore housing two Matrix-Multiply Units (MXUs), a vector unit, and a scalar unit. A Trillium VM can contain 1, 4, or 8 chips; slices of 4 chips and smaller share the same NUMA node. Trillium shares much of its architecture with v5e but brings significant advancements.

v6e TPU host - CPU0 and CPU1 each connect over PCIe to TPU chips across NUMA 0 and NUMA 1, chips linked by the ICI network; a 1-chip VM and a 4-chip VM are highlighted
A v6e (Trillium) TPU host - CPUs connect to chips over PCIe within each NUMA node; chips are linked by the ICI network. A VM can carve out 1, 4, or 8 chips (a 1-chip and a 4-chip VM shown).

Specify it: TPU API - use AcceleratorType, e.g. v6e-8 for an 8-TensorCore slice. GKE API - use --machine-type, e.g. t6e-standard-8t.

NumbersTrillium key benefits (vs. v5e)
  • Massive performance boost - significantly higher peak compute and bandwidth per chip.
  • Increased memory - double the HBM capacity and bandwidth per chip.
  • SparseCore - v6e adds SparseCores to accelerate embedding-heavy models (common in recommendation systems).
  • Optimized for - transformer, text-to-image, and convolutional neural network (CNN) training, fine-tuning, and serving.

TPU v5p

TPU v5p is a high-performance accelerator distinguished by its scale and 3D interconnect topology. Each v5p chip contains a TensorCore with four MXUs, a vector unit, and a scalar unit. All 4x4x4 (one cube) and larger v5p slices have full 3D torus connectivity; slices smaller than a full cube are 3D connected but lack the wrap-around links that define a true 3D torus.

Numbersv5p supported configurations
  • Pod size - 8,960 chips with flexible, high-speed networking, configurable into various slice shapes.
  • Single-slice training - supported up to 6,144 chips.
  • Multislice - scale further, up to 18,432 chips.

Specify it: TPU API - use AcceleratorType as v$VERSION_NUMBERp-$CORES_COUNT, e.g. v5p-256 is a slice with 256 TensorCores (128 chips). GKE API - all v5p TPU VMs use the ct5p-hightpu-4t machine type.

GotchaICI resiliency is on by default for v5p

Like TPU v4, ICI resiliency is enabled by default for v5p slices that are one cube or larger (e.g. v5p-128, a 4x4x4 config). It improves fault tolerance and scheduling availability.

A four-rack TPU v5e pod, front view
A four-rack TPU v5e pod - v5e is the cost-efficient sibling that Trillium (v6e) builds on.

TPU v4

TPU v4 provides a powerful, flexible platform, noted for its 3D mesh interconnect topology. Each TPU v4 chip contains two TensorCores; each TensorCore has four MXUs, a vector unit, and a scalar unit.

TPU v4 virtual core - two TensorCores, each with a scalar unit, vector unit, and four matrix-multiplication units, flanked by high-bandwidth memory
A TPU v4 chip exposes a virtual core of two TensorCores; each TensorCore holds a scalar unit, a vector unit, and four matrix-multiplication units, with high-bandwidth memory on each side.

3D mesh vs. 3D torus - v4 chips connect directly to their nearest neighbors in three dimensions (a 3D mesh). For topologies where dimensions are 2A=B=C or 2A=2B=C, the connections can be configured as a 3D torus, which generally gives better performance thanks to improved communication paths.

Common TPU v4 topologies - 2x2x1 (4 chips, 8 cores), 2x2x2 (8/16), 2x2x4 (16/32), 2x4x4 (32/64), 4x4x4 (64/128)
Common TPU v4 topologies - each cube shape maps to a chip and core count, from 2x2x1 (4 chips, 8 cores) up to 4x4x4 (64 chips, 128 cores).
Numbersv4 enhancements (vs. v3)
  • NUMA locality - v4 supports non-uniform memory access; bind your training script to NUMA node 0 to raise memory throughput, especially for CPU-heavy workloads.
  • Unified HBM - a unified 32-GiB HBM space across both TensorCores improves coordination.
  • Enhanced HBM and DMA - latest HBM standards and better direct memory access for high-performance striding.
  • TensorCore improvements - doubled MXUs, higher clock rates, more transposition/permutation bandwidth, and faster MXU weight loading.

Recap

A dense comparison of the generally available versions:

Chip metricv5eTrillium (v6e)*v4v5p
Chips per pod2562564,0968,960
Bf16 TFLOPs197918 (4.7x)275459
Int8 / FP8 TOPs3941,836 (4.7x)N/A918
HBM per chip (GB)1632 (2x)3296
HBM BW (GB/s)8201,640 (2x)1,2282,765
ICI BW per chip (GB/s)400 bi-dir800 bi-dir (2x)600 bi-dir1,200 bi-dir
DCN BW per chip (Gb/s)25100 (4x)5050
SparseCore (embeddings)NoYes (new)YesYes

*Trillium multipliers are relative to v5e.

For exam recall, tie each milestone to its version:

MilestoneVersion
First public Cloud TPU with scalable slices and a 2D torus interconnectv2
First to deploy optical circuit switches (OCS) for dynamic interconnect reconfigurationv4
Large-scale 3D interconnect topology with high HBM capacityv5p
DECISIONWhich TPU generation?
Large-scale inference / AI agentsIronwood (v7e) - purpose-built for inference, highest performance per watt
Transformer, text-to-image, CNN + embeddingsTrillium (v6e) - SparseCore, 2x HBM vs v5e
Very large training at maximum scalev5p - 8,960-chip pod, 3D torus, ICI resiliency by default
Flexible training with 3D mesh/torusv4 - NUMA locality, unified HBM
Cost-efficient workloadsv5e - the value tier Trillium builds on
Pick this when: Ironwood for large-scale inference; Trillium for transformer/text-to-image/CNN + embeddings; v5p for the largest training runs; v4 for flexible 3D-mesh training