@Scale
Inference latency has replaced algorithmic design as the binding constraint for autonomous agents, forcing hardware architectures to shift from raw training throughput to custom on-die memory and low-diameter network fabrics.
AI-assisted summary of Architecting Infrastructure for the AI Native Future: Scaling Autonomous Agents on Google TPUs — original source. Check the original for full context.
Source published:
Key ideas
- Google outlined its latest TPU hardware innovations designed specifically for autonomous AI agents, highlighting the throughput-oriented TPU 8T and latency-optimized TPU 8i architectures. (2:27)
- TPU 8T scales to 9,600 chips per pod via Optical Circuit Switches (OCS), reaching 121 exaflops of FP4 compute while cutting networking power by 40% and costs by 30% compared to electronic switches. (8:41)
- The TPU 8i introduces the hierarchical 'Boardfly' interconnect topology across 1,152 chips, reducing network diameter by 53% and cutting distributed inference latency by over 50%. (14:25)
- Google's VirgoNet fabric links more than 134,000 TPU chips across a single data center building and scales beyond 1 million TPUs when unified across global WAN networks. (10:45)
Detailed notes
## Background Presented by Sabastian Mugazambi from Google and published on YouTube by the @Scale channel on June 19, 2026, this conference presentation examines how physical infrastructure has become the primary bottleneck for AI innovation. The accompanying description highlights how Google TPU generations are architected to support the massive throughput and low-latency inference demanded by recommendation engines, Mixture-of-Experts models, and emerging autonomous agents.
## TL;DR As autonomous AI agents shift workloads toward continuous execution, expansive context windows, and real-time reasoning loops, hardware infrastructure must fundamentally evolve to sustain agentic cognition. Google addresses these demands through specialized silicon—pairing throughput-focused TPU 8T clusters for pre-training and decodes with latency-optimized TPU 8i chips featuring massive on-chip SRAM and direct vector streaming. Scale-up and scale-out are achieved using Optical Circuit Switching (OCS), the datacenter-wide VirgoNet fabric, and the three-tiered Boardfly interconnect topology that cuts network diameter by over 50%. Ultimately, these low-latency architectural co-designs lay the essential groundwork for training frontier interactive world models and real-time physical AI.
## Atmosphere & style The presentation carries the polished, authoritative, and direct tone of a tier-one systems architecture keynote. Mugazambi delivers the technical breakdown with measured precision, methodically unpacking deep silicon microarchitecture, optical fabrics, and distributed routing without getting bogged down in marketing jargon. It feels like an insider look into the physical realities of hyperscale AI, creating an engaging tension between low-level hardware constraints and the high-concept future of real-time autonomous reasoning.
## Bulletin - [02:27](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=147s) Google outlined its latest TPU hardware innovations designed specifically for autonomous AI agents, highlighting the throughput-oriented TPU 8T and latency-optimized TPU 8i architectures. - [08:41](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=521s) TPU 8T scales to 9,600 chips per pod via Optical Circuit Switches (OCS), reaching 121 exaflops of FP4 compute while cutting networking power by 40% and costs by 30% compared to electronic switches. - [14:25](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=865s) The TPU 8i introduces the hierarchical 'Boardfly' interconnect topology across 1,152 chips, reducing network diameter by 53% and cutting distributed inference latency by over 50%. - [10:45](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=645s) Google's VirgoNet fabric links more than 134,000 TPU chips across a single data center building and scales beyond 1 million TPUs when unified across global WAN networks.
## Key takeaways - [00:00](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=0s) The primary bottleneck for AI progress has shifted from pure algorithmic design to physical compute and networking infrastructure capable of handling autonomous agents at scale. - [00:00](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=0s) Autonomous agents require continuous execution across thousands of instances, long-horizon context windows, and real-time reasoning loops, pushing pre-training MoEs up to 10 trillion parameters. - [02:27](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=147s) Unlike general-purpose serial CPUs or parallel GPUs, Google TPUs are custom-engineered specialist ASICs optimized explicitly for matrix multiplication and high arithmetic intensity. - [05:02](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=302s) Moving block scale multiplication inside the MXUs removes VPU overhead during quantized matrix multiplications, improving Model FLOPs Utilization (MFU) across FP4, FP8, and BF16 formats. - [05:02](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=302s) Dedicated Sparse Cores on TPU 8T feature an LLM decoder engine that allows overlapping prompt prefill on Tensor Cores with autoregressive decode phases. - [05:02](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=302s) TPU RDMA and TPU Direct Storage bypass host CPU memory entirely, enabling ultra-long KV caches to stream directly between managed storage and HBM. - [08:41](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=521s) Racks built as 64-chip 3D torus cubes are dynamically interconnected using Optical Circuit Switching (OCS), avoiding electronic packet switches and physical recabling. - [10:45](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=645s) Google's VirgoNet fabric offers non-blocking connectivity for over 134,000 TPUs within a single facility and achieves 40% lower training latency. - [10:45](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=645s) Inference latency functions as a cognitive constraint for agent utility, because multi-step internal reasoning loops compound small delays into massive systemic latencies. - [12:18](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=738s) The latency-optimized TPU 8i places high-capacity SRAM on-die adjacent to compute units, enabling KV caches to reside beside MXUs and bypassing off-chip memory fetch penalties. - [12:18](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=738s) A specialized collective acceleration engine on TPU 8i delivers a 5× latency reduction for collective communication primitives. - [14:25](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=865s) The three-tier Boardfly topology connects 4 chips per board, 32 chips per rack group, and 1,152 chips per pod via OCS, halving end-to-end communication latency. - [15:32](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=932s) Emerging interactive world models and physical robotics demand millisecond reaction times, allowing autonomous agents to simulate thousands of lifetimes in virtual environments before physical deployment.
## Detailed walkthrough ### [00:00](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=0s) The Demands of Autonomous AI Agents on Infrastructure
The rapid emergence of AI agents is stretching infrastructure far beyond its traditional boundaries. Unlike one-off queries, autonomous agents require continuous execution across thousands of concurrent instances. This demands massive throughput from AI accelerators as a fundamental prerequisite for continuous, real-time autonomy. Furthermore, these agents operate across long-horizon tasks, requiring expansive context windows—the core working memory that grounds agents in deep situational awareness and enables sustained multi-step task execution.
```mermaid flowchart TD accTitle: AI Agent Demands on Hardware Infrastructure accDescr: Three foundational requirements driven by autonomous agents: high throughput, vast context windows, and low-latency inference.
subgraph AgentNeeds["Core Demands of Autonomous Agents"] direction LR TP["Continuous Execution<br/>(Massive Accelerator Throughput)"] CW["Long-Horizon Tasks<br/>(Vast Context Windows & Memory)"] RT["Real-Time Reasoning<br/>(Low-Latency Memory Access & High-Speed Inference)"] end
subgraph Lifecycle["Impact Across Model Lifecycle"] direction LR Pre["Pre-Training MoEs<br/>(Up to 10T Parameters)"] RL["Reinforcement Learning<br/>(Multi-Step Reasoning Loops)"] Serve["Serving Hundreds of Thousands<br/>(Ultra-Low Latency Orchestration)"] end
AgentNeeds --> Lifecycle ```
These operational constraints span the entire development lifecycle of the agentic era: - **Pre-training:** Driving massive Mixture-of-Experts (MoE) architectures that now scale up to 10 trillion parameters, requiring specialized, high-throughput hardware. - **Post-training & Reasoning:** Employing reinforcement learning techniques such as sampling and iterative test-time reasoning loops before deployment to boost accuracy and efficiency. - **Serving at Scale:** Orchestrating hundreds of thousands of agents that are continuously prompting and awaiting immediate responses.
Because of this shift across the entire pipeline, the fundamental bottleneck for AI innovation is no longer purely algorithmic design; it has expanded to encompass the underlying physical infrastructure.
---
[02:27](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=147s) Compute Paradigms and a Decade of Google TPU Evolution
When evaluating AI and machine learning compute engines, processors fall into three distinct philosophical camps: - **CPUs:** "Generalist and serial thinkers." While highly versatile and flexible, they are bottlenecked by workloads requiring massive throughput. - **GPUs:** "Generalist, but they're parallel thinkers." Highly capable across graphics and parallel ML workloads, leveraging parallelism to avoid throughput choke points. - **TPUs:** "Specialists." Custom-engineered specifically for matrix multiplications—the fundamental mathematical operation behind modern neural networks.
Google has developed custom Tensor Processing Units for more than a decade, beginning with TPU v1 in 2015, specifically designed to break through the arithmetic intensity and interconnect walls that throttle agentic systems. Over that decade, Google introduced distributed shared memory across Inter-Chip Interconnects (ICI), direct liquid cooling, and 3D torus topologies to knit chips together into coherent supercomputers. The presentation highlights the newly announced TPU v6e and TPU v6p (referred to as TPU 8T and TPU 8i/TPU v8 generations).
Reimagining accelerator systems requires end-to-end co-design: - Custom silicon features tailored to matrix math. - Proprietary low-latency Inter-Chip Interconnect (ICI) topologies. - Data-center-wide scale-out fabric. - Physical infrastructure innovations, including vertical power delivery directly to the die and advanced liquid cooling.
---
[05:02](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=302s) Inside TPU v8: MXUs, Sparse Cores, and Direct Storage
Focusing on the throughput-optimized TPU silicon (TPU 8T), each Tensor Core incorporates Matrix Multiply Units (MXUs), Vector Processing Units (VPUs), and Activation Units (AXUs). The architecture supports low-precision arithmetic spanning FP4, FP8, and BF16, as well as mixed-precision workflows.
A notable microarchitectural advancement is moving block scale multiplication directly inside the MXUs rather than handling it on the VPUs. This provides zero VPU overhead for quantized matrix multiplications, delivering higher Model Flops Utilization (MFU) alongside high precision. The core relies on systolic arrays, which pipeline inputs directly through computational grids rather than fetching back and forth between memory and compute units on every cycle, ensuring the MXUs are continuously fed without stalling.
```mermaid flowchart LR accTitle: Direct TPU Memory Transfer Architectures accDescr: TPU RDMA and Direct Storage bypass host memory for ultra-low latency transfers.
subgraph RDMA["TPU RDMA"] T1["TPU A HBM"] <-->|"Direct via NIC (Zero Host Hop)"| T2["TPU B HBM"] end
subgraph Storage["TPU Direct Storage"] MS["Managed Storage<br/>(Long-Context KV Cache)"] -->|"Direct DMA to HBM"| T3["TPU HBM"] end ```
Beyond the dense Tensor Core, TPU silicon includes specialized **Sparse Cores**: - **Embeddings Acceleration:** Historically used in recommendation models to overlap dense compute layers (on Tensor Cores) with embeddings operations offloaded to the Sparse Cores. - **LLM Decoder Engine:** TPU 8T adds a dedicated LLM decoder engine to the Sparse Cores, granting them sufficient arithmetic intensity to overlap prefill execution on Tensor Cores with auto-regressive decode execution on the Sparse Cores.
For memory and data ingestion, Google eliminates host CPU memory hops entirely: - **TPU RDMA:** Directly streams data between the High Bandwidth Memory (HBM) of two separate TPUs via Network Interface Cards (NICs). - **TPU Direct Storage:** Allows TPU HBM to stream data directly to and from managed external storage. This enables ultra-long context KV caches to live on managed storage and swap into HBM without passing through host DRAM.
---
[08:41](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=521s) Scale-Up via 3D Torus and Optical Circuit Switching (OCS)
To scale up accelerators into a unified coherent unit, TPUs use a throughput-optimized 3D torus ICI topology. Every TPU connects directly to adjacent neighbors using wrap-around links, forming a tightly coupled cube of 64 chips that physically populates a single data center rack.
```mermaid flowchart TD accTitle: Optical Circuit Switching TPU Scale-Up Architecture accDescr: Optical Circuit Switches dynamically route fiber connections between 64-chip TPU 3D torus cubes to create a 9600-chip supercomputer.
subgraph TorusCubes["Racks (3D Torus Cubes)"] C1["Cube X<br/>(64 TPU Chips)"] C2["Cube Y<br/>(64 TPU Chips)"] C3["Cube Z<br/>(64 TPU Chips)"] end
subgraph Switching["Software-Controlled Routing"] OCS["Optical Circuit Switches (OCS)<br/>Direct Dynamic Fiber Reconfiguration"] end
C1 <--> OCS OCS <--> C2 OCS <--> C3 ```
Single racks are then interconnected using Optical Circuit Switching (OCS) over optical fiber paths: - **Cluster Scale:** Up to 9,600 TPU chips integrated into a single supercomputer pod. - **Compute Performance:** 121 exaflops of FP4 peak performance. - **Aggregated Memory & Bandwidth:** Over 2 petabytes of shared HBM and over 19 terabits per second of bidirectional ICI bandwidth per node. - **Software Reconfigurability:** OCS allows an input fiber from one rack/cube to be dynamically switched and pointed to another cube in software without physical recabling or manual intervention. - **Efficiency Gains:** OCS eliminates electronic packet switches in the optical path, yielding 30% lower cost and 40% lower power draw while unlocking arbitrary topological reconfigurations optimized for dynamic model and data parallelism.
---
[10:45](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=645s) Scale-Out Networking: VirgoNet and Planetary Clusters
Scaling out beyond single ICI pods into hundreds of thousands of chips requires purpose-built data center fabrics. Google introduced the **Virgo Net** architecture for TPU 8T:
- **Datacenter-Scale Fabric:** Scales across an entire physical building, providing a non-blocking fabric linking over 134,000 TPU chips. - **Global WAN Expansion:** Interconnecting multiple VirgoNet fabrics via Google's distributed global Wide Area Network (WAN) unlocks distributed training superclusters exceeding 1 million TPU chips. - **Latency Optimization:** Delivers 40% lower latency during large-scale distributed training phases.
Turning to agent serving, the speaker emphasizes that low-latency inference is "the real hero of the agentic era." Latency is no longer merely a user experience metric—it has transitioned into an explicit "cognitive constraint" governing agent utility. Because autonomous agents execute internal reasoning iterations, search loops, and tool calls, high latency rapidly compounds into catastrophic systemic delays and elevated iteration costs.
[12:18](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=738s) Purpose-Built Silicon for Low-Latency Inference
An autonomous agent is fundamentally only as reliable as the consistency of its underlying model execution and the hardware fabric powering it. To deliver the responsiveness required for real-world agentic workflows, Google designed latency-optimized silicon, introduced here as the TPU 8i. The processor incorporates architectural enhancements explicitly targeted at slashing inference latency, beginning with an exceptionally large SRAM capacity placed directly on-die. By positioning a substantial SRAM adjacent to the primary compute blocks, the chip can retain frequently accessed execution state—most notably the transformer key-value (KV) cache—directly beside the compute units, dramatically curbing the high latency penalty of repeatedly fetching memory from off-chip storage.
```mermaid flowchart TD accTitle: TPU Data Streaming Architecture accDescr: Diagram contrasting typical GPU cache movement with TPU shared vector memory and MXU streaming.
subgraph GPU_Flow ["Conventional GPU Pipeline"] G_L2["L2 Cache"] --> G_L1["L1 Cache"] G_L1 --> G_TC["Tensor Cores (Small Tiles)"] end
subgraph TPU_Flow ["TPU Low-Latency Pipeline"] T_IN["Large Inputs"] --> T_SVM["Shared Vector Memory"] T_SVM -->|"Streamlined Stream"| T_MXU["Matrix Multiplication Units (MXUs)"] T_SRAM["Large On-Chip SRAM (KV Cache)"] -.->|"Near-Compute Access"| T_MXU end ```
Beyond on-chip memory sizing, chip-to-chip bandwidth has been significantly scaled up. Inter-chip interconnect (ICI) bandwidth and chip-to-chip communication speeds were doubled, and Google integrated a specialized collective acceleration engine that achieves an additional 5× latency reduction for collective communication primitives. This dataflow design directly challenges conventional architectures:
> "When you really think about low latency inference, you have to be efficient in how you moving data from the memory onto the computational units. In a typical GPU floor, you have data moving from the L2 cache to the L1 to the tensor cores where operations are happening on the small tiles. But on the other hand with TPUs, large inputs are copied to the shared vector memory. And these large inputs are further streamlined to the matrix multiplication units."
By continuously saturating the matrix multiplication units (MXUs) with wide streams of data rather than bottlenecking on fragmented tile transfers, the hardware maintains exceptionally high Model FLOPs Utilization (MFU), ensuring compute engines stay constantly busy.
- **High-Capacity On-Chip SRAM**: Houses large KV caches adjacent to compute engines to eliminate off-chip memory fetch overheads. - **Doubled Interconnect Bandwidth**: 2× speed and bandwidth increase across direct chip-to-chip interfaces. - **Dedicated Collective Acceleration Engine**: Hardware acceleration reducing collective communication latency by 5×. - **Direct Vector-to-MXU Streaming**: Shared vector memory architecture designed to bypass hierarchical cache bottlenecks and maximize sustained compute utilization.
---
[14:25](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=865s) The Boardfly Hierarchical Interconnect Topology
Scaling inference clusters past a handful of chips demands rethinking network topologies beyond classical multi-dimensional tori. To scale clusters efficiently, Google introduced the "Boardfly" topology for TPU 8i, a non-torus hierarchical interconnect architecture capable of linking up to 1,152 chips within a single tightly coupled pod. The hierarchy is organized in three modular stages from the board level up to the optical switching layer:
```mermaid flowchart TD accTitle: Boardfly Hierarchical Interconnect Topology accDescr: Three-level hierarchy showing TPU boards, rack groups, and optical circuit switches linking 1152 chips.
subgraph Level1 ["Level 1: Board"] B_CHIPS["4 Fully Connected TPU Chips"] end
subgraph Level2 ["Level 2: Group / Rack"] R_BOARDS["8 Fully Connected Boards (32 Chips)"] end
subgraph Level3 ["Level 3: Pod Fabric"] OCS["Optical Circuit Switches (OCS)"] POD["36 Connected Groups (1,152 TPU Chips)"] end
B_CHIPS --> R_BOARDS R_BOARDS --> OCS OCS --> POD ```
At the base of the topology, four TPU chips are fully connected to one another on an individual board. Eight of these boards are then fully interconnected to construct a group—representing a physical rack on the datacenter floor housing 32 chips. Finally, 36 of these rack groups are bound together through Google's Optical Circuit Switches (OCS) to assemble the full 1,152-chip pod.
By structuring the network hierarchically rather than routing across a large multi-hop torus, the Boardfly topology achieves a 53% reduction in network diameter between any two arbitrary chips across the entire 1,152-node fabric. This drastic reduction in physical network traversals translates directly into a greater than 50% end-to-end latency improvement across distributed inference and collective communication jobs.
---
[15:32](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=932s) The Frontier: World Models, Physical AI, and Real-Time Reasoning
Looking ahead, the frontier of machine learning workloads is shifting decisively toward extreme low-latency inference. While language-based autonomous agents are already driving rapid progress, frontier agents increasingly demand far more inference cycles to execute deep reasoning steps and internal deliberation per second. Simultaneously, this trajectory intersects with two emergent technical paradigms: interactive world models and physical AI.
World models dynamically synthesize interactive, frame-by-frame simulations reflecting real-world physical dynamics in real time. This capability completely changes how autonomous agents are developed:
> "What this means is that you could actually take AI agents and have them operate and practice operating in this simulated real-time environment before you actually have them perform tasks in the real world where they're now more trained and more accurate."
In parallel, physical AI—spanning humanoid robotics and autonomous vehicles—demands reaction times operating strictly in the millisecond regime, making sustained, low-latency execution non-negotiable. The eventual convergence of world models and physical robotics allows autonomous systems to simulate thousands of lifetimes of physical actions safely inside high-throughput virtual worlds before deploying into physical hardware. Mugazambi concludes by noting Google's excitement for this trajectory, emphasizing that continuous custom hardware innovation across the TPU lineage is engineered specifically to satisfy the computational and latency requirements of this AI-native future.
## Notable quotes > [02:27](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=147s) Generalist and serial thinkers. — Sabastian Mugazambi
> [02:27](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=147s) Generalist, but they're parallel thinkers. — Sabastian Mugazambi
> [02:27](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=147s) Specialists. — Sabastian Mugazambi
> [10:45](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=645s) the real hero of the agentic era. — Sabastian Mugazambi
> [10:45](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=645s) cognitive constraint — Sabastian Mugazambi
> [12:18](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=738s) When you really think about low latency inference, you have to be efficient in how you moving data from the memory onto the computational units. In a typical GPU floor, you have data moving from the L2 cache to the L1 to the tensor cores where operations are happening on the small tiles. But on the other hand with TPUs, large inputs are copied to the shared vector memory. And these large inputs are further streamlined to the matrix multiplication units. — Sabastian Mugazambi
> [15:32](https://www.youtube.com/watch?v=MUxbhxzIMpQ&t=932s) What this means is that you could actually take AI agents and have them operate and practice operating in this simulated real-time environment before you actually have them perform tasks in the real world where they're now more trained and more accurate. — Sabastian Mugazambi
## Mentioned Google, Sabastian Mugazambi, @Scale Conference, TPU (Tensor Processing Unit), TPU v1, TPU v6e, TPU v6p, TPU 8T, TPU 8i, CPU, GPU, Matrix Multiply Unit (MXU), Vector Processing Unit (VPU), Activation Unit (AXU), Sparse Core, High Bandwidth Memory (HBM), Inter-Chip Interconnect (ICI), Optical Circuit Switch (OCS), VirgoNet, Boardfly topology
## Video description Architecting Infrastructure for the AI Native Future: Scaling Autonomous Agents on Google TPUs by Sabastian Mugazambi from Google
As the industry pivots toward an "AI Native" paradigm, the bottleneck for innovation has shifted from algorithmic design to the underlying infrastructure's ability to handle unprecedented scale and complexity. This session explores how Google TPU (Tensor Processing Unit) infrastructure serves as the catalyst for this transformation, specifically within the domains of large-scale Recommender Systems, MoEs, LLMs and the emerging era of Autonomous Agents.
We will delve into the architectural innovations of the latest TPU generations, demonstrating how their purpose-built design facilitates the massive throughput required for real-time recommendation engines and the high-speed inference necessary for agentic orchestration.
Want to learn more about the @Scale Conference? Visit our website here: atscaleconference.com
[Source](https://www.youtube.com/watch?v=MUxbhxzIMpQ)