# Google Cloud — GKE dynamic slicing for higher resilience, and efficiency for TPUs

- Company: Google Cloud (cloud.google.com)
- Announced: 2026-11-09T13:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://cloud.google.com/blog/products/containers-kubernetes/gke-dynamic-slicing-on-tpus/
- Record: https://forck.live/items/33406-gke-dynamic-slicing-for-higher-resilience-and-efficiency-for-tpus
- Subject: Gemini Enterprise

Running large-scale AI workloads on TPU and Google Kubernetes Engine (GKE) requires infrastructure that adapts as fast as your models change. To help, dynamic slicing decouples logical TPU slice formation from physical nodepool provisioning. Compared to creating a static nodepool for each TPU slice, dynamic slicing reduces AI workload startup times by up to 5x and workload recovery by 4.5x — maximizing TPU goodput, efficiency, and workload resilience at scale. GKE dynamic slicing is generally available. Beyond one workload, one nodepool Previously, managing TPU capacity at GKE standard required separate, fixed TPU slice topology nodepools, increasing startup times and complexity while preventing multi-host nodepools from hosting multiple AI workloads. Changing workload needs meant manually deleting and recreating nodepools. Additionally, this tight coupling created large failure domains where a single hardware fault crashed an entire slice, slowing recovery while reprovisioning. …

---

Record: https://forck.live/items/33406-gke-dynamic-slicing-for-higher-resilience-and-efficiency-for-tpus
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md
