You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Status: Draft for community feedback Authors: Lance Wang @wang2yn84
1. Motivation
Tunix currently leverages Pathways on Cloud for multi-host training, which offers robust distributed runtime and TPU support. However, there are strong reasons to add Multi-Controller JAX (McJAX) as an alternative multi-host backend:
TRC Compatibility: Google’s TRC (Tensor Research Cloud) clusters do not support GKE/Pathways setups, but do support McJAX.
Broader Familiarity: Many open-source and academic users already use McJAX for distributed runs (via SSH or Slurm launchers).
Open Availability: Pathways is not yet fully open-sourced, , limiting reproducibility for non-Google users.
Adding McJAX support enables Tunix to run seamlessly on TPUs, GPUs, and CPUs in multi-host environments without relying on GKE or proprietary infra.
2. Goals & Non-Goals
Goals
Provide multi-host training for Tunix using McJAX, supporting both TPU and GPU platforms.
Maintain API compatibility with existing Pathways code (resharding API).
Offer launcher scripts for SSH and Slurm clusters (e.g., TRC).
Support fault-tolerant checkpointing via Orbax for McJAX topologies.
Ensure interoperability — Pathways and McJAX can co-exist via environment flag.
Non-Goals
Re-implement Pathways runtime features such as autoscaling or elastic jobs.
Guarantee full feature parity across all hardware configurations at day one.
3. Background
Pathways provides a cloud-native single-controller runtime, integrating with GKE and TPU VM topologies. It’s widely used internally but has limited public availability.
McJAX is a simpler, open alternative for distributed JAX training across multiple controllers, communicating over gRPC or RDMA or NCCL.
4 Implementation Phases
**M0 | Identify the suitable library for distributed system handling
**M1 | McJAX env prototype on single host | Launch single controller successfully
**M2 | 2-host TPU v5e-8 | Verify distributed Jax works
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Status: Draft for community feedback
Authors: Lance Wang @wang2yn84
1. Motivation
Tunix currently leverages Pathways on Cloud for multi-host training, which offers robust distributed runtime and TPU support. However, there are strong reasons to add Multi-Controller JAX (McJAX) as an alternative multi-host backend:
Adding McJAX support enables Tunix to run seamlessly on TPUs, GPUs, and CPUs in multi-host environments without relying on GKE or proprietary infra.
2. Goals & Non-Goals
Goals
Non-Goals
3. Background
4 Implementation Phases
Beta Was this translation helpful? Give feedback.
All reactions