Skip to main content

4 posts tagged with "TPU 8t"

Google TPU 8t training chip

View all tags

TPU v8 四季度进入量产:8t/8i 拆分与 2027 年 910 万颗出货预测

· 3 min read
Industry Research Team

2026 年 10 月,多家台系供应链调研给出同一判断:Google TPU v8 将在本季度(2026 Q4)进入硬件供应链量产阶段,2027 年成为明显放量年。TPU 从第八代起首次拆分为训练与推理两条产品线,这个变化的影响不亚于性能提升本身。

出货预测:402 万到 910 万颗​

凯基证券 2026 年 10 月报告的核心数字(供应链口径,非 Google 官方):

项目2026 年2027 年(预估)
TPU v8 总出货量约 402 万颗约 910 万颗(+126%)
v8t(训练)—约 360 万颗
v8i(推理)—约 550 万颗
机柜出货—翻倍成长

需求侧最大的公开客户是 Anthropic:2025 年宣布扩至最高 100 万颗 TPU(超 1 GW),2026 年 4 月又与 Google、博通签署新协议,取得数 GW 的下一代 TPU(v8)产能,2027 年上线支撑 Claude 前沿模型。

8t 与 8i:第一次按负载拆分​

此前每一代 TPU 都同时承担训练与推理。v8 首次分化:

  • TPU 8t(市场分析代号 Zebrafish):训练专用,延续 3D Torus scale-up 架构,单 SuperPod 可扩展至 9,600 颗;面向大模型预训练与 embedding 密集负载。集成 Arm Axion CPU(Google 自研 64 核 Neoverse V2),TPU 与 CPU 协同。
  • TPU 8i(市场分析代号 Sunfish):推理专用,采用全新的 Boardfly 片间互联(ICI)拓扑,单 Pod 最多 1,152 颗 active TPU;面向后训练、采样、实时推理与推理型负载。

系统级升级同样激进:散热从芯片液冷升级为系统级液冷(单柜水冷价值约 4.5-5 万美元),电源引入**高压直流(HVDC)**架构(10kW PSU),PCB/载板大尺寸化。这意味着 v8 机柜的供应商结构比 v7 复杂得多——鸿海在 v8 拿到 TPU 层与 L11 机柜组装份额,Celestica 仍是 L10/L11 主力。

两个口径提醒​

  1. 代工伙伴归属有矛盾。Google Cloud Next 官方材料与部分供应链调研对 v8t/v8i 分别由博通还是联发科参与开发说法相反。本站两代卡片的处理方式是:正文保留官方活动口径,预测数字标注为凯基证券口径,采购与研究引用时请注明来源层级。
  2. 「出货量」不等于「可购买量」。v8 产能优先供应 Google 内部(Gemini、DeepMind)与 Anthropic 等大客户,外部云上可租用的 v8 实例预计要等 2027 年才逐步铺开。

对行业格局的意义​

TPU v8 放量 + Maia 300 部署 + Trainium 扩产,意味着 2027 年「非 NVIDIA 推理算力」的供给盘子里,自研 ASIC 将首次占到可观份额。对模型厂商,这意味着更低的推理单位成本与更强的议价筹码;对 NVIDIA,压力主要落在推理侧,训练侧的 CUDA 护城河短期无虞。

相关阅读​

谷歌第八代 TPU 拆分战略:TPU 8t 主攻训练、TPU 8i 专精推理

· 8 min read
Industry Research Team

在 2026 年 4 月 22 日拉斯维加斯 Google Cloud Next '26 大会上,谷歌发布了第八代 TPU 的两款新品——训练专用的 TPU 8t 与推理优化的 TPU 8i。这是谷歌 TPU 家族诞生以来,第一次将训练与推理拆分至独立芯片。这一决策不仅重新定义了 TPU 的产品形态,也向整个 AI 算力行业释放了一个明确信号:训练与推理的工作负载特征已经分化到"一颗芯片通吃"不再经济的程度。

为什么要把训练和推理拆开​

传统上,TPU 一直走"一芯多用"路线——第七代 Ironwood 虽然以推理为主,但训练与推理仍在同一产品线上。而大模型进入智能体(Agentic AI)时代后,两种负载的差异被急剧放大:

  • 训练追求极限吞吐与集群扩展性,需要海量 HBM 容量、超高互联带宽,对单次推理延迟不敏感;
  • 推理则被成本、延迟和能效三重约束,KV Cache 读取、解码阶段的内存墙问题远比算力峰值更重要。

用同一颗芯片兼顾两者,必然在架构上互相妥协。谷歌选择彻底拆分:8t 的命名即"第 8 代 + training",8i 即"第 8 代 + inference"。谷歌基础设施负责人 Amin Vahdat 对此表态:"业界将受益于针对训练和推理各自需求专门优化的芯片。" CEO 皮查伊则从商业视角补充:谷歌要"以成本效益方式提供数百万智能体所需的大规模吞吐和低延迟"。

TPU 8t:训练专用,单 Pod 121 EFLOPS​

根据站内芯片卡数据,TPU 8t 的核心规格如下:

项目TPU 8t(训练专用)
制程TSMC 2nm
Die 设计双计算 Die
单芯片 FP4 算力12.6 PFLOPS
显存8× HBM3e 12 层(约 216GB)
HBM 带宽约 7 TB/s
Pod 规模9,600 芯片
Pod HBM 总量2 PB
Pod FP4 算力121 EFLOPS(约为 Ironwood 的 3 倍)
集成 CPUArm Axion(64 核 Neoverse V2)
TDP1,300 W
代工合作博通(Broadcom)
云端上线2026 H2

TPU 8t 有几个值得展开的架构要点。

其一,SparseCore 加速器。 8t 专门配备 SparseCore 处理嵌入查找(embedding lookup)带来的不规则内存访问模式——这正是 MoE 架构和推荐系统训练中最拖累 GPU 利用率的环节。站内卡显示其原生支持 Expert Parallel、1M+ token 长上下文训练以及 DPO/PPO/GRPO 等在线强化学习后训练范式。

其二,超大规模组网。 单 Pod 9,600 颗芯片经 ICI 3D Torus 与 Virgo 网络互联,单设施可扩展至 134,000 卡、跨站点扩展至 100 万卡以上,通过 JAX/Pathways 软件栈实现单集群超百万块 TPU 的协同训练。这意味着 Gemini 级别的 frontier 模型可以在单一 Pod 内完成训练。

其三,代际性能跃升。 谷歌官方口径是:同价格下 TPU 8t 性能达上代的 2.8 倍,每瓦性能提升 124%——训练侧的"每美元 token"经济学再次被改写。

TPU 8i:推理专精,384MB SRAM 加持​

TPU 8i 则把刀刃对准了推理成本。它的规格取向与 8t 截然不同:

项目TPU 8i(推理专用)
制程TSMC 2nm
核心设计双张量核心 + CAE(集合通信加速引擎)
片上 SRAM384 MB(Ironwood 的 3 倍)
显存288 GB HBM3e
Pod 规模1,152 芯片
Pod FP8 算力11.6 EFLOPS
性价比较 Ironwood 提升 80%
能效较 Ironwood 提升 117%
散热风冷 / 液冷均可
代工合作联发科(MediaTek,首次)

三个细节尤其关键。第一,384MB 片上 SRAM 大幅缓解长上下文 KV Cache 的内存墙,配合 CAE 将集合通信延迟降低 5 倍,KV Cache 可跨芯片共享。第二,288GB 单芯片显存是当前最大显存的推理 ASIC,FP16 下可完整装载 70B 模型。第三,风冷可选意味着不需要液冷机房也能部署,把推理集群的落地门槛大幅拉低。

Gemini API、Vertex AI 推理、Anthropic Claude on Vertex 的在线服务均面向 TPU 8i 设计。性能提升 80%、每瓦性能提升 117%,加上单美元算力比 Ironwood 高约 70% 的推测口径,8i 的目标非常直白:让"每百万 token 成本"继续下探。

两款芯片的镜像对比​

指标TPU 8t(训练)TPU 8i(推理)
核心设计双计算 Die双张量核心 + CAE
片上 SRAM—384 MB
Pod 芯片数9,6001,152
Pod 算力121 EFLOPS FP411.6 EFLOPS FP8
Pod HBM2 PB—
集成 CPUArm Axion无
散热第四代液冷风冷/液冷
代工博通联发科

一个耐人寻味的差异:只有 8t 集成了 Arm Axion CPU。训练节点需要 CPU 做海量数据预处理与加载,而推理节点的瓶颈在芯片内部,主机侧负担较轻。这也说明 Axion 集成并非营销噱头,而是精确的负载驱动设计。

Axion 集成:全栈协同的深层意图​

Arm Axion 是谷歌自研的 64 核 Neoverse V2 CPU。将其集成进 TPU 节点,意味着 TPU 不再是纯粹的"加速器",而是 TPU + CPU 协同的"超节点"——对标 NVIDIA 的 Vera CPU + Rubin GPU 组合。数据预处理、权重初始化、推理调度全部在节点内完成,消除了传统架构中主机 CPU 与加速器之间的数据搬运瓶颈。这是谷歌全栈(自研 CPU、自研 TPU、自研网络、自研框架)协同能力的集中体现。

与 NVIDIA 通用路线的分野​

谷歌的训练/推理拆分并非孤例。华为昇腾已经走出了同款路线——昇腾 950PR 面向训练、950DT 面向推理,同样是"代际相同、形态分化"。而 NVIDIA 至今坚持一颗 GPU 通吃训练与推理的通用路线,靠 CUDA 生态和 product segmentation(B 系列 / inference 专用 SKU)来分层。

两条路线的优劣可以放进一张表:

维度专用拆分(谷歌/华为)通用 GPU(NVIDIA)
单位成本效率各负载最优化,性价比更高存在为通用性付出的冗余
软件生态需维护两套工具链CUDA 一套通吃
客户灵活性训练/推理集群需分别采购一套集群弹性调度
演进节奏每条线独立迭代单一代际整体升级

对于自用负载极其明确的第一方厂商(谷歌、华为),拆分的经济性压倒一切;而 NVIDIA 面向的是千行百业的混合负载,通用性才是护城河。

TPU 生态的外溢:Google 之外正在成型​

还有一条容易被忽视的线索:TPU 正在从"谷歌内部资产"变成"开放生态"。前谷歌基础设施 VP Bikash Koley 跳槽至 TPU neocloud 创业公司 Crux AI——以 TPU 算力为核心商品、依托 Google Cloud 之外的基础设施提供云服务的商业层正在成型。加上 Anthropic 等重量级 TPU 大客户的存在,TPU 已经事实上成为 CUDA 之外最成熟的 AI 算力生态。两款芯片将于 2026 年晚些时候对外供应,届时 TPU 云市场的竞争格局值得持续观察。

小结​

TPU 8t 与 8i 的拆分,标志着 AI 算力竞争从"单芯片性能竞赛"进入"负载分化设计"的新阶段。训练芯片拼集群规模与吞吐,推理芯片拼每瓦、每美元与延迟——两种优化方向已经无法在单一架构内调和。谷歌用 TSMC 2nm、Axion 集成、SparseCore 与 CAE 给出了自己的答卷;华为昇腾的 PR/DT 双线则证明这不是孤立的赌注。对整个行业而言,2026 H2 这两款芯片正式对外供应后的市场反馈,将决定"训练/推理拆分"是否会成为下一代 AI 加速器的默认范式。

Hot Chips 2026 Full Recap: Rubin, MI455X, Crescent Island Together as AI Compute Delivery Enters the "System-Level" Era

· 7 min read
Industry Research Team

August 23-25, 2026, the 38th Hot Chips (HC38) was held at Stanford's Memorial Auditorium. As the bellwether of global high-performance chip architecture, this conference landed exactly at the most intense moment of the AI compute arms race — the official agenda had 48 entries, including 7 AI accelerators, 6 memory tutorials, 6 CPUs, and 4 each of GPUs and networking. Putting the vendor talks together, one consensus emerged: the unit of AI compute competition has shifted from "single chip" to "whole rack / entire system."


1. Overview: Three Days of Agenda, Almost a Preview of the 2027 AI Rack Market​

Monday (8/24) afternoon's GPU session was the focus, with four talks nearly colliding as the 2027 AI rack market:

  • NVIDIA Rubin GPU ("Driving the Era of Agentic AI"): First chiplet-architecture GPU, 288GB HBM4, ~50 PFLOPS FP4, paired with 88-core Arm-architecture Vera CPU into NVL72 / NVL144 racks, mass production in H2 2026.
  • AMD Instinct MI400 (two talks: architecture + system architecture): Told the "rack-scale" story thoroughly.
  • Intel Crescent Island: A 350W air-cooled card designed for Agentic AI inference.

Tuesday (8/25) afternoon's AI session was almost a parade of "hyperscalers de-NVIDIA-izing": Google's 8th-gen TPU, OpenAI's first custom chip, Microsoft Maia 200, Meta MTIA, and Cerebras wafer-scale rack all appeared together.

Every vendor on stage used the term "Agentic AI" within the first two PPT slides — not a coincidence, but the collective shift in 2026 AI workload design goals.


2. NVIDIA Rubin: One Rack Is a Supercomputer​

What NVIDIA featured at Hot Chips was not a single GPU but the Vera Rubin NVL72 whole cabinet — 72 Rubin GPUs + 36 Vera CPUs, 18 compute trays + 9 NVLink switch trays, about 1.3 million components, nearly 1,300 chips, weighing about 4,000 pounds (~1.8 tons).

The single Rubin GPU specs are equally stunning:

MetricRubin GPUvs Blackwell
Transistors336 billion (TSMC 3nm dual-die)208 billion (+61.5%)
Memory288GB HBM4—
Bandwidth22 TB/s2.8× Blackwell
NVFP4 inference50 PFLOPS5× GB200
Training compute35 PFLOPS3.5×

The most disruptive design is in the compute tray: no cables, no hoses, no fans, all interconnected via the PCB backplane. NVIDIA says assembly time dropped from nearly 2 hours to 5 minutes (20× faster) while improving maintainability.

This time NVIDIA is selling not FLOPS but tokens per megawatt. Citing a SemiAnalysis benchmark based on DeepSeek-v4-PRO (140K+ context, AgentX workload), it claims: versus GB300 NVL72, Vera Rubin NVL72 delivers 10× to up to 30× tokens/MW as interaction intensity rises. A single cabinet provides 3.6 EFLOPS inference compute, whole-cabinet power 190-230kW; long-term capacity target is 1,000 NVL72 cabinets per day.


3. AMD MI455X + Helios: Bigger Memory and Open Interconnect​

AMD's answer is the MI455X + Helios rack going head-to-head with NVIDIA. MI455X uses CDNA 5 architecture, 8 N2-process accelerator dies + N3P-process interconnect die, 256 workgroup processors, 192MB global L2.

MetricMI455Xvs Rubin
Memory432GB HBM4 (12-layer stack)50% higher than Rubin's 288GB
Bandwidth23.3 TB/sSlightly ahead
MXFP4 compute40.26 PFLOPS—
System (Helios 72 cards)2.9 ExaFLOPS FP4 inference—
Price~$5.25M per cabinet—

At the system level, AMD bets on the UALoE (Ultra Accelerator Link over Ethernet) open standard: each GPU provides 3.6 TB/s bidirectional interconnect bandwidth; two 512-port 200G UALoE switch chips in the switch tray total 10.8 TB/s — opening the interconnect protocol to the whole industry while targeting NVLink.

Production cadence: AMD plans to deliver engineering samples and small-batch systems in H2 2026, with large-scale ramp in Q2 2027. Earlier rumors of Helios delay due to cooling issues were not confirmed by AMD.


4. Intel Crescent Island: The Air-Cooled, Large-Memory "Cost-Effective Oddball"​

Intel offers a completely different path: Crescent Island — a 350W, air-cooled, standard-PCIe-slot inference GPU designed for Agentic AI, with the key metric being tokens per watt.

MetricCrescent IslandNote
ArchitectureXe3P, 32 Xe cores, 32MB unified L2Disclosed at Hot Chips
MemoryIntel branded card 160GB / ODM up to 480GB LPDDR5XMore than Rubin's 288GB HBM4
Form factor350W air-cooled PCIePlugs into standard racks, no liquid-cooling retrofit
RASECC, dynamic page offline, hard-package repair, PCIe advanced error reportingAddresses "silent data corruption"

Intel's logic is clear: inference scenarios need far more memory capacity than bandwidth; using low-cost LPDDR5X for capacity and air cooling to skip liquid-cooling infrastructure drives down per-token cost. Combined with Diamond Rapids Xeon (256 performance cores, 1.28GB cache, 128 PCIe Gen6 lanes), Intel tries to surround from edge to datacenter with "CPU + inference GPU + open software stack."


5. Custom ASIC Parade: Google, OpenAI, Microsoft, Meta Together​

Tuesday afternoon's AI session was the most historic of the conference — a parade of "hyperscalers de-NVIDIA-izing":

ChipVendor / PartnerPositioningKey Specs / Progress
TPU 8t (Sunfish)Google × BroadcomTraining9,600 cards per pod, 121 FP4 ExaFLOPS, 2PB shared HBM
TPU 8i (Zebrafish)Google × MediaTekInference288GB HBM, 384MB on-chip SRAM (3× prev gen), ICI 19.2 Tb/s
JalapeñoOpenAI × BroadcomInference9-month end-to-end design, target ~50% token cost cut, commercial end of 2026
Maia 200Microsoft (TSMC 3nm)Inference140B+ transistors, 10+ PFLOPS FP4, 216GB HBM3E, serving GPT-5.2 at Des Moines datacenter
MTIA 300-500Meta (RISC-V) × BroadcomTraining + inferenceUp to 25× compute gain, one model every 6 months before 2027

Google split TPU into training (8t) and inference (8i) dedicated architectures for the first time — its biggest architectural shift in a decade. Norm Jouppi personally took the stage to present TPU v8.


6. Two Hidden Threads — Memory and Networking: HBM4 Year 1 + AI Factory OS​

Beyond GPUs/ASICs, two hidden threads mattered equally:

  • Memory: Samsung's HBM Base Die (logic-process base die) and SK hynix's advanced packaging appeared together; the HBM4-era "base-die foundry" industry shift begins; HBF (high-bandwidth flash), LPDDR5X-PIM, 3D DRAM, and CXL compute-storage showcased "compute-in-memory" moving from papers to products.
  • Networking: NVIDIA BlueField-4 (DPU) and Spectrum-X Multiplane architecture (presented by Gilad Shainer) — networking is becoming the decisive architecture for gigascale AI, scaling from hundreds of thousands to a million cards; Broadcom Thor Ultra Ethernet NIC keeps pressing; Mojo Vision showed chip-level optical I/O.

7. Three Routes, One Consensus​

At the same conference, three vendors offered three distinctly different AI compute delivery philosophies:

  1. NVIDIA: Full-stack closed integration — GPU, CPU, DPU, and switch chips all self-designed, pushing system performance to the extreme via ultimate software-hardware co-design, at the cost of deep customer lock-in.
  2. AMD: Open-standard catch-up — Uses larger HBM4 capacity + UALoE open interconnect for a "cost-effective + open" play, tearing open the inference gap with Meta and OpenAI's 12GW-class orders.
  3. Intel: Air-cooled cost-effectiveness — Abandons liquid cooling and HBM, uses LPDDR5X large memory + standard PCIe, betting that "most inference doesn't need a 200kW rack."

But all three agree: the unit of competition is no longer the chip, but the co-designed system (rack / system). For buyers, 2027 compute planning should compare not "single-card PFLOPS" but "tokens per megawatt, latency, availability, and full-lifecycle cost."

References​


This article is compiled from Hot Chips 2026 (Aug 23-25) official presentations and on-site reports from ServeTheHome, SemiAnalysis, TechPowerUp, etc. Performance data are vendor-disclosed figures; actual performance subject to mass-produced products.

Google TPU 8i/8t Officially Launched: Training and Inference Split for the First Time, 2nm Process Powers the Agentic Era

· 7 min read
Industry Research Team

On April 22, 2026, at Google Cloud Next '26 in Las Vegas, Google officially launched its 8th-generation Tensor Processing Unit (TPU). For the first time in Google's history, it split AI training and inference onto two independent chips:

  • TPU 8t: designed for model training
  • TPU 8i: focused on high-concurrency inference

This launch introduces no new physical concept, but focuses on solving the core pain points of AI data centers: ten-thousand-card cluster scaling efficiency, Agentic AI workload optimization, and performance per watt.

TPU 8i (inference-specific): eliminating the "waiting room effect"​

TPU 8i is the first inference-specific chip co-designed by Google and MediaTek, aimed at eliminating the "waiting room effect" — where user requests are intentionally queued or delayed to maximize hardware utilization.

TPU 8i core specs (estimated)​

ParameterTPU 8iTPU v7 Ironwood
PositioningInference-specificMostly inference
ProcessTSMC 2nm—
Die designDual compute die (est.)—
Memory8× HBM3e 12-layer (~192GB est.)8× HBM3 (192GB)
Memory bandwidth~7 TB/s (est.)7,380 GB/s
FP8 compute~4,614 TFLOPS (est.)4,614 TFLOPS
TDP (per chip)1,300 W1,000 W
InterconnectICI 3D TorusICI 3D Torus
Integrated CPUArm Axion (64 cores)None
CoolingAir or liquid4th-gen liquid
Announced2026-04-222025-08-25
Mass productionEnd of 20272026

Key features:

  • ✅ High-concurrency inference optimization: built for Agentic AI, supports inference chains of thousands of steps
  • ✅ Arm Axion CPU integration: 64-core Neoverse V2, host CPU + data preprocessing synergy
  • ✅ Low latency: eliminates the "waiting room effect", extremely low TTFT (time to first token)
  • ✅ 117% better performance per watt: vs Ironwood (at equal price)

TPU 8t (training-specific): the "engine" of Gemini 3/4​

TPU 8t is designed for training Google's frontier models like Gemini 3 / Gemini 4, continuing Google's long-term partnership with Broadcom.

TPU 8t core specs​

ParameterTPU 8tTPU v7 IronwoodImprovement
PositioningTraining-specificMostly inferenceForm-factor split
ProcessTSMC 2nm—New gen
Die designDual compute die—Architecture upgrade
Memory8× HBM3e 12-layer (~256GB per chip est.)8× HBM3 (192GB)Upgrade
Memory bandwidth~7 TB/s (per chip est.)7,380 GB/sFlat
Pod chip count9,600 chips9,216+4%
Pod total HBM2 PB—Far exceeds
Pod FP4 compute121 EFLOPS~42 EFLOPS (est.)~3×
Integrated CPUArm Axion (64 cores)NoneNew
TDP (per chip)1,300 W1,000 W+30%
Mass productionEnd of 20272026—

Key features:

  • ✅ Native MoE training support: Expert-Parallel optimization (DeepSeek / Mixtral style)
  • ✅ Long-context training: 1M+ token context training optimization
  • ✅ RLHF / post-training: native Online RL (DPO/PPO/GRPO) optimization
  • ✅ Arm Axion CPU synergy: data preprocessing / weight init offloaded to CPU
  • ✅ SparseCore acceleration: MoE routing and recommendation systems

Strategic significance of the 8th-generation TPU​

1. Training and inference split for the first time​

Previously, Google's TPU design philosophy was "one architecture for both training and inference" (e.g., TPU v5p, v6e). But the arrival of the Agentic AI era changed that:

  • Training workloads: large-scale matrix multiply, long-sequence backpropagation, sparse MoE
  • Inference workloads: high concurrency, low latency, KV Cache-intensive, dynamic batching

These two workloads impose very different demands on chip architecture. After the split:

  • TPU 8t can focus on optimizing compute density and memory capacity
  • TPU 8i can focus on optimizing inference throughput and performance per watt

2. Dual-track partnership with Broadcom and MediaTek​

  • Broadcom: continues designing TPU 8t (training), extending the long-term partnership since TPU v1
  • MediaTek: first-time collaboration designing TPU 8i (inference), bringing mobile-chip low-power design expertise

This "dual-track" strategy lets Google:

  • Pursue peak performance on training chips (combined with Broadcom's high-end ASIC experience)
  • Pursue peak energy efficiency on inference chips (combined with MediaTek's mobile-chip experience)

3. Versus NVIDIA Vera Rubin​

ComparisonGoogle TPU 8t + 8iNVIDIA Vera Rubin
StrategyTraining/inference splitUnified architecture (GPU+CPU)
ProcessTSMC 2nmTSMC 3nm (est.)
EcosystemGoogle Cloud onlyGlobally available
SoftwareJAX / PyTorch-XLACUDA / PyTorch
Mass productionEnd of 2027Fall 2026
StrengthDeep Gemini integrationMost mature ecosystem

Deep technical analysis​

TSMC 2nm: why 2nm?​

Google is the first vendor to adopt TSMC 2nm on an AI accelerator (NVIDIA Rubin uses 3nm). 2nm (N2) vs 3nm (N3E):

  • Transistor density: ~15-20% higher
  • Power reduction: ~25-30% (at equal performance)
  • Performance gain: ~10-15% (at equal power)

For TPU 8t/8i, which already hit 1,300W, 2nm is mandatory — otherwise 4nm/3nm couldn't integrate dual compute dies and 8× HBM3e within reasonable power.

Arm Axion CPU: Google's in-house CPU enters the TPU node for the first time​

Previously, TPU nodes used Intel Xeon or AMD EPYC as host CPUs. TPU 8t/8i integrate Google's in-house Arm Axion CPU (64-core Neoverse V2) for the first time:

Significance:

  1. Data preprocessing offload: tokenization, data augmentation can run entirely on Axion, freeing TPU compute
  2. Weight initialization: large-model training weight init on CPU, accelerating training startup
  3. Inference scheduling: Axion handles request scheduling and load balancing for multi-model inference

This marks the TPU node's evolution toward a "SuperNode": no longer a pure accelerator, but a TPU + Axion CPU co-design system, comparable to NVIDIA's Vera CPU.

4th-gen liquid cooling: the 1,300W thermal challenge​

TPU 8t/8i TDP reaches 1,300W (30% over Ironwood's 1,000W), posing a huge data-center cooling challenge.

Google adopts a 4th-gen liquid cooling solution:

  • Cold-plate liquid cooling: directly cools GPU die and HBM
  • Immersion cooling: optional (ultra-high-density deployment)
  • Smart thermal control: dynamically adjusts pump speed and fan RPM by workload

Production timeline and use cases​

TimeEvent
2026-04-22Cloud Next '26 official announcement
H2 2026Internal testing (Google DeepMind first)
End of 2027Mass production, Google Cloud availability
2028Next-gen TPU (possibly TPU 9)

Target use cases:

  • ✅ Frontier model training (Gemini 3/4, external customers)
  • ✅ MoE large-model inference (high concurrency, low latency)
  • ✅ Multimodal AI (ViT + LLM simultaneous inference)
  • ✅ Agentic AI (Agentic AI workloads)

Competitive comparison​

VendorProductProcessTDPMass production
GoogleTPU 8i (inference)TSMC 2nm1,300WEnd of 2027
GoogleTPU 8t (training)TSMC 2nm1,300WEnd of 2027
NVIDIARubin GPUTSMC 3nm (est.)~1,000WFall 2026
NVIDIAVera CPUTSMC 3nm (est.)~500WFall 2026
AMDMI455X (MI400)TSMC 3nm (est.)~700W2026
HuaweiAscend 950PR—~500WQ1 2026

Industry impact​

  1. AI chips enter the 2nm era: Google leads with TSMC 2nm; NVIDIA and AMD will follow
  2. Training/inference split becomes a new trend: other vendors (NVIDIA, AMD) may follow suit
  3. In-house CPUs become standard: Google (Axion), NVIDIA (Vera), Huawei (Kunpeng) all do CPU+accelerator co-design
  4. Liquid cooling becomes inevitable: 1,300W TDP means air cooling can no longer suffice

References​


This article is compiled from Google's official announcements and public sources; some specs are estimates, subject to final official release.