Menu

1 / 3

PyTorch 2.15 Rollback Has Two Boundaries. Only One Is a Setting.

DEV Community: pytorch·NTCTech·1 day ago
#Qa5XiedA
#devtopytorch#devto#dev#checkpoint#release
Reading 0:00
15s threshold

PyTorch 2.15 gives an operator two ways back to 2.14, and only one of them is a setting. The new NCCL backend can be switched to the legacy implementation with a backend string or an environment variable. The checkpoint format cannot be switched at all: according to the release notes, a checkpoint written by 2.15 cannot be loaded by 2.14 or earlier, and there is no flag to write the old format. The first is a temporary configuration fallback. The second is a state-compatibility boundary. They are independent, they expire on different terms, and a rollback plan that counts them as one will be wrong about the second.

The New NCCL Default Has a One-Release Exit

In PyTorch 2.15, backend="nccl" is also the default CUDA backend of init_process_group() , and it now creates the rewritten NCCL implementation. The legacy implementation stays available as backend="nccl-legacy" for this release only. The release notes say nccl-legacy and TORCH_DIST_USE_NCCL2=0 will be removed in the next release.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.