Bringing PyTorch Monarch to AMD GPUs: Single-Controller Distributed Training on ROCm – PyTorch

Search

Close Search

Blog

Bringing PyTorch Monarch to AMD GPUs: Single-Controller Distributed Training on ROCm

By AMD: Chaojun Hou, Liz Li, Zachary Streeter, Xinyu Kang, Lei Zhang, Yuankai Chen, Yao Fu, Wen Chen, Zhenyu Gu, Andy Luo │ Meta: Matthias Reso, Hamid Shojanazeri, Monarch teamJuly 6, 2026No Comments

Featured projects

Training state-of-the-art large language models (LLMs) with billions of parameters requires distributed training across hundreds or thousands of GPUs. At this scale, hardware failures are not exceptional events—they are expected. A single GPU memory error, network partition, or node crash can bring down an entire training run that has been progressing for days or weeks. While our previous work demonstrated near-linear scaling of FP8 training at scale (achieving 96.16% scaling efficiency on a 1024-GPU MI325 cluster with DeepSeekV3-671B), the key challenge remains: reliability at scale.

To address these challenges, we have brought PyTorch Monarch to AMD Instinct GPUs with ROCm, expanding the single-controller model beyond CUDA environments and bringing this emerging runtime to a broader hardware ecosystem.

In this blog, we will explore the architecture of PyTorch Monarch, walk through the engineering effort required to port Monarch’s GPU runtime and distributed communication stack to ROCm, and demonstrate how the system dynamically recovers from node failures without halting the entire training job. By the end, you will understand how Monarch enables elastic, fault-tolerant distributed training on AMD GPUs and why this represents a significant step toward stable, large-scale AI infrastructure.

The Challenge: Reliability at Scale

Traditional fault-tolerance strategies rely heavily on periodic checkpointing: saving the full model state to persistent storage at regular intervals. When a failure occurs, the entire job restarts from the last checkpoint. While conceptually simple, this approach has significant drawbacks.

Challenge<br>Impact

Checkpoint overhead<br>Writing hundreds of gigabytes of model state to storage consumes time and I/O bandwidth.

Wasted computation<br>All progress since the last checkpoint is lost upon failure.

Cluster idle time<br>The entire cluster sits idle while the failed node is replaced and the job restarts.

Scalability limits<br>As cluster size grows, the probability of failure during any checkpoint interval increases.

For truly large-scale training, scaling is not enough—training must also recover from failures. We need a more dynamic approach, one that allows healthy nodes to continue training while failed nodes recover and rejoin, minimizing wasted computation and maximizing GPU utilization. This is where PyTorch Monarch comes in.

What is PyTorch Monarch?

PyTorch Monarch introduces a new distributed programming paradigm that enables developers to orchestrate entire GPU clusters from a single Python program. With its actor-based runtime, process mesh abstraction, and asynchronous execution model, Monarch simplifies large-scale distributed training and enables complex workflows that combine training, evaluation, and reinforcement learning within one unified script.

The architecture operates at multiple distinct levels:

Python API : A single-program interface where developers write simple Python code to get distributed GPU execution.

Monarch Runtime : Manages actors and meshes, supervision trees, and tensor sharding.

Rust Runtime (Tokio) : Ensures high performance and memory safety.

Infrastructure : Integrates with RDMA, RCCL/NCCL, SLURM, Kubernetes, and SkyPilot.

Figure 1: PyTorch Monarch architecture decoupling Python API from the Rust runtime and infrastructure.

By decoupling the parallelism strategy used within each training replica from the fault-tolerance mechanism used across replicas, Monarch provides a cleaner fault-tolerance model. Failures are isolated (actors have private state, crashes do not propagate), hierarchical (handled at the lowest possible level), and recovery is fast (seconds for local restart, minutes only if escalated).

Figure 2: Monarch’s hierarchical fault-handling model and supervision tree.

Porting Monarch to ROCm: Ecosystem Integration

Bringing Monarch to AMD GPUs required significant engineering effort to port the GPU runtime and distributed communication stack to ROCm.

We successfully implemented three main porting paths:

Collective Communications : We used hipify_torch to convert the C++ bridge code from CUDA to HIP and linked against RCCL, which mirrors NCCL’s API.

GPU Memory Management : We extended the build system to auto-detect the platform and route CUDA driver API calls through their HIP equivalents.

RDMA Integration : Configuring GPU_PLATFORM=rocm keeps the libibverbs-based RDMA path intact while swapping the GPU-side bindings from CUDA to HIP for GPU-direct transfers.

Figure 3: Porting Monarch from CUDA to...