# Google and Meta Open-source TorchTPU for Native PyTorch Integration TorchTPU enables seamless execution of PyTorch workloads on Google TPU hardware infrastructure. - **Source:** [InfoQ](https://brifing.si/source/68ac18af-a4f3-4f7c-9c2c-44d4af8f89dd) - **Published:** 2026-11-02 - **Topic:** [Software & Engineering](https://brifing.si/c/engineering) - **Original article:** - **On Brifing:** https://brifing.si/s/c95dd700-0151-471e-8815-19e0f3f19d27 ## Native PyTorch Backend Launch Google and Meta have introduced TorchTPU, an open-source project providing a native PyTorch backend for Google TPUs. This initiative allows developers to execute PyTorch workloads on TPU hardware with minimal code changes. It supports eager execution, compiled modes, and distributed computing, marking a significant shift from previous integration methods used by engineers. ## Moving Beyond PyTorch/XLA Since 2020, Google relied on PyTorch/XLA, which utilized JAX and XLA for hardware acceleration. However, this approach required intrusive source-code modifications and suffered from severe compile-time latency. It also lacked support for native imperative eager execution, creating friction for developers who needed to define explicit compilable regions within their existing model architectures. ## Simplified Migration Workflow Migrating from GPUs to TPUs now involves replacing the cuda device with tpu and switching the nccl distributed backend to tpu_dist. Alternatively, developers can utilize the new torch.accelerator.current_accelerator API to identify available hardware. These changes significantly reduce the technical overhead previously required to port complex deep learning models to TPU environments. ## Advanced Eager Execution Modes TorchTPU introduces three distinct eager execution modes: strict, debug, and DeferAndFuse. The DeferAndFuse hybrid mode is particularly notable, as Google claims it achieves performance gains of 50% or more over strict eager execution. This mode also reduces peak HBM memory usage, providing better efficiency for large-scale training and inference tasks on TPUs. ## Extensive Validation Pipeline To ensure compatibility, Google integrated a testing pipeline evaluating 5,000 Hugging Face models across 500 architectures. Testing focused on TPUv5e hardware generations and beyond, using corpus stratification to balance real-world adoption with architectural diversity. This methodology ensures that production-grade weights are thoroughly evaluated before deployment, minimizing risks for teams adopting the new backend. ## Performance Benchmarking Results Testing a 30-billion parameter Muse Glimmer model on a single TPUv7 chip yielded 25.7k token/s inference throughput at 5120 sequence length. Training performance on four TPUv7 chips reached 5.6k token/s. Additionally, Google scaled Qwen3 MoE 235B training workloads from 1,024 to 8,192 TPUv7 chips, demonstrating competitive performance-per-dollar for large-scale mixture-of-experts models. ## Enterprise Deployment Context Beyond cloud availability via GCP, Google provides TPUs to enterprise clients for on-premises deployments. Current users include Anthropic, with Meta potentially following in the future. This hardware accessibility strategy aims to broaden the reach of TPU infrastructure, allowing organizations to leverage specialized hardware for their internal AI research and production workloads. ## Future Development Roadmap TorchTPU remains in an early stage of evolution with active development ongoing. The roadmap prioritizes improvements in dynamic shapes, compilation performance, and operator coverage. Future updates will also focus on reinforcement learning and quantization support. These enhancements are critical for maintaining parity with the rapidly evolving PyTorch ecosystem and emerging AI requirements. ## Sources covering this story - https://www.infoq.com/news/2026/11/torchtpu-native-pythorch-tpu/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global — --- _Summary written by Brifing from the original reporting. Copyright in the original article belongs to its publisher; read the full piece at the link above._