PyTorch migrates libtorch-extract jobs from EC2 to OSDC
Cost and efficiency boost: standalone CI jobs now run on OSDC instead of EC2.
PyTorch has merged a critical infrastructure optimization: commit 132b16e migrates libtorch-extract jobs from EC2 to OSDC (Open Source Data Center). These jobs were running on EC2 linux.4xlarge instances because standalone workflows bypass the arc-enabled reusable system, which normally remaps to OSDC. By moving them directly to OSDC, PyTorch reduces dependency on expensive EC2 compute and leverages more cost-effective internal infrastructure.
The migration is platform-aware. Linux extraction requires debug symbol splitting (strip/objcopy) and now uses the same manylinux builder image as the source wheel — the image tag is threaded through the extraction config to guarantee availability. Windows extraction simply unpacks wheels with Python stdlib, so it runs in a standard python:3.11 container on the same OSDC runner. The change affects both Linux manywheel and Windows wheel binary workflows, and was generated using the CI workflow generation script to ensure only intended workflows were modified.
- Standalone libtorch-extract jobs bypassed arc.yaml and ran on EC2 linux.4xlarge; now they run on OSDC
- Linux extraction uses the same manylinux builder image tag as the build job for guaranteed image existence
- Windows extraction uses python:3.11 on the same OSDC runner, skipping debug symbol splitting
Why It Matters
Reduces cloud costs and improves CI reliability for PyTorch's massive open-source project with 102k stars.