Decoupled DiLoCo: Resilient Distributed Training Across Data Centers with Low Bandwidth

Google DeepMind published a paper on Decoupled DiLoCo (Distributed Low-Communication), a distributed training architecture that decouples compute into separate "learner units" that communicate asynchronously. This allows training large models across geographically distributed data centers with much lower bandwidth requirements than traditional synchronized approaches.
Key Details
- Builds on two prior advances: Pathways (asynchronous data flow system) and DiLoCo (reduced bandwidth between data centers).
- Training is split across decoupled learner units — independent compute islands. A chip failure in one unit doesn't interrupt the others. The system is self-healing: after losing an entire learner unit to hardware failure, training continues and the unit is seamlessly reintegrated once it recovers.
- Validated with chaos engineering — injected artificial hardware failures during training runs. Decoupled DiLoCo maintained high "goodput" (useful training time) while conventional methods nosedived under failure.
- Trained a 12 billion parameter model across four separate U.S. regions using 2-5 Gbps wide-area networking — achievable with existing internet connectivity between datacenters.
- Achieved the same benchmarked ML performance (tested with Gemma 4 models) as conventional training approaches.
- Reported more than 20× faster than conventional synchronization methods because communication is overlapped with computation, avoiding blocking bottlenecks.
Architecture Overview
The system incorporates communication into longer computation periods instead of requiring synchronous all-reduce across all chips. This avoids "blocking" where one part of the system must wait for another. The result is resilient training that can tap unused compute anywhere, turning stranded resources into useful capacity.
Who It's For
Teams training large language models or other frontier models across multiple data centers who need fault tolerance without sacrificing performance or requiring custom network infrastructure.
📖 Read the full source: HN AI Agents
👀 See Also

Claude Opus 4.7 Flags Hantavirus Vaccine Questions as Safety Risk, Pausing Chats
Asking Claude Opus 4.7 how to develop a hantavirus vaccine triggers safety filters pausing the chat, while Sonnet 4.6 also blocks related predictive modeling.

Reddit User Argues Developers Should Shift from Clean Coding to Model Architecture with AI Agents
A Reddit post argues that developers using AI coding agents like Claude should stop focusing on writing clean code and instead become 'model architects' who orchestrate AI systems. The author shares specific techniques including creating 'logic maps' before coding and treating prompts as design reviews.

Claude Agent SDK Billing Changes June 15: Per-User Credits, No Rollover, Hard Cliff
Starting June 15, Claude Agent SDK usage and claude -p stop counting against subscription limits. Each user gets a separate monthly credit (e.g., Pro $20, Max 5x $100). Credits don't pool, don't roll over, and have a hard cliff.

Firefox 148 adds AI kill switch and enhanced privacy controls
Firefox 148 introduces an AI kill switch feature that lets users disable all AI functionalities, including chatbot prompts and AI-generated link summaries. The update also provides more control over remote updates and data collection.