TechByteByByte

TPU

The chip Google built after realizing that three minutes of voice search a day, run at scale, would force it to double its entire data center footprint.

#tpu#google#hardware#infrastructure-serving-phase

The GPU article covered hardware repurposed for AI almost by accident. This article covers the opposite: a chip designed from scratch, specifically for AI, in direct response to a real, alarming internal calculation — the TPU, or Tensor Processing Unit.

The simple definition

A TPU is a custom chip, called an ASIC (Application-Specific Integrated Circuit), designed by Google specifically for neural network computation, rather than adapted from another purpose like graphics rendering. Recall from the GPU article’s core insight — a GPU’s parallelism happens to suit AI well, but it wasn’t built for that purpose. A TPU is the deliberate opposite: every part of its design exists specifically to make the exact matrix multiplication covered throughout the Neural Networks phase as fast and efficient as physically possible, with nothing else in mind.

The real, genuinely alarming calculation that started this project

This deserves to be told precisely, because it’s a real, documented moment of institutional panic that directly explains why TPUs exist at all.

In 2013, Google engineers calculated that if people used Google’s voice search for just three minutes a day, and Google ran the deep neural networks powering that speech recognition on its existing CPU and GPU infrastructure at that scale, the company would need to double the number of data centers it operated just to keep up. That’s not a minor inefficiency — it’s an existential infrastructure problem.

Google responded by designing the TPU from the ground up specifically for neural network inference, and moved with remarkable speed: from first tested silicon to running live production applications inside Google’s data centers took just 22 days, and the entire project went from design to deployment in about 15 months, remarkably fast for custom chip development, which usually takes years.

flowchart LR
    A["2013: 3 min/day of voice search would require doubling Google's data centers"] --> B[Design a custom chip specifically for neural network math]
    B --> C[TPU: deployed within 15 months]
    C --> D["Real result: 15-30x higher performance, 30-80x better performance-per-watt vs. contemporary CPUs/GPUs"]

ANALOGY vs. TECHNICAL REALITY

Analogy: Think of the difference between using a general-purpose kitchen (a GPU, adaptable to many kinds of cooking) versus building a dedicated, single-purpose factory line that does nothing but stamp out one specific shape of metal part, as efficiently as physically possible. The dedicated factory line can’t cook anything else, but for that one specific job, it will always beat a flexible kitchen on both speed and cost per unit.

Where this breaks down: A factory line is a physical, mechanical system. A TPU’s specialization is achieved through its actual circuit design — Google’s own published research describes it tolerating reduced computational precision specifically because neural networks don’t need the same numerical exactness other computing tasks do, letting far more computational units fit onto the same chip, a design choice covered fully in the Quantization article later in this phase.

What Google’s own published numbers actually showed

This is worth stating precisely, since it’s real, documented, and genuinely striking. Google’s own 2017 in-depth performance study found the first-generation TPU delivered 15 to 30 times higher performance, and 30 to 80 times better performance-per-watt, compared to contemporary CPUs and GPUs on the specific neural network inference workloads it was tested against — an order-of-magnitude improvement, not an incremental one, on exactly the problem that had originally threatened to double Google’s infrastructure footprint.

A concrete example, layered

For a simple beginner example: a TPU board is compact enough to fit into a hard-disk-drive slot within a standard data center server rack, reflecting how tightly Google optimized the entire package for real, physical deployment at scale, not just raw computational throughput. For a production example: Google’s real, current TPU generations power Gemini and other Google AI products directly, and Google Cloud offers TPUs for rent to external developers and companies, a genuine, commercially available alternative to Nvidia’s GPU-based cloud offerings for anyone training or serving large models.

Why TPUs haven’t simply replaced GPUs across the industry

It’s worth being honest about a real, genuine trade-off here. A TPU’s specialization is also its limitation — it’s tailored specifically for the kind of matrix computation neural networks need, and originally, tightly coupled to Google’s own TensorFlow framework. GPUs, by contrast, remain more broadly flexible and are supported by a much larger, more mature software ecosystem, covered in the next article’s discussion of CUDA — which is precisely why most of the industry outside Google, including OpenAI and Anthropic, has continued to rely primarily on GPUs rather than switching to TPUs.

Common misconception

What moves through a TPU

TensorFlow or JAX program
        -> compiler arranges the operations
        -> TPU matrix units perform the work
        -> high-bandwidth memory supplies tensors
        -> results move to the next operation

A TPU is not a complete AI model. It is specialized hardware on which training or inference calculations can run.

A current Gemini connection

Google’s seventh-generation TPU is called Ironwood. Google announced it in April 2025 with a design focused on the growing amount of inference work, then announced general availability in November 2025.

Google reported that Ironwood offers more than 4 times better performance per chip for training and inference than its sixth-generation Trillium TPU, and 10 times the peak performance of TPU v5p. Google also states that Gemini, Veo, Imagen, and Anthropic’s Claude train and serve on TPUs.

These are vendor measurements and product statements. They explain real deployment, but a fair purchase comparison still needs the same model, batch size, precision, latency target, and software setup on every system.

GPU or TPU?

  • Choose based on the framework, model support, cloud availability, team knowledge, cost, and measured workload performance.
  • A GPU often offers a broad software ecosystem and deployment choices.
  • A TPU can be especially attractive for workloads already built around Google’s supported stack and cloud infrastructure.

Verified sources

A frequent beginner assumption: that a TPU is simply Google’s own branded version of a GPU, functionally interchangeable with one. As this article has explained, a TPU’s architecture is genuinely different at the hardware level — an ASIC built from scratch for one specific kind of computation, rather than a repurposed graphics chip — even though both chips end up serving the same broad purpose of accelerating neural network math.

Where this fits in what comes next

You now understand both major categories of hardware powering modern AI — GPUs’ repurposed parallelism and TPUs’ purpose-built design. The next article, CUDA, covers the software layer that actually makes GPU hardware usable for AI computation at all — a genuinely necessary piece Nvidia had to build over a full decade, years before the AI boom made it valuable.

In one sentence

A TPU is a custom chip Google designed from scratch specifically for neural network computation, born from a real 2013 calculation that voice search alone would otherwise require doubling Google’s data centers, and its published 15-30x performance advantage over contemporary hardware remains one of the most concrete, documented cases of purpose-built AI hardware outperforming general-purpose chips.

Author
TechByteByByte Editorial Team
Reviewed by
TechByteByByte Admin
Published
Last reviewed