Detect accelerator type when backend is not specified #142216
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/142216
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit bf1aec7 with merge base 61dc5e9 ( This comment was automatically generated by Dr. CI and updates every 15 minutes. |
pytorch-bot
bot
added
oncall: distributed
wconstab
approved these changes
Dec 6, 2024
XilunWu
approved these changes
Dec 6, 2024
|
@pytorchbot merge |
Merge startedYour change will be merged once all checks pass (ETA 0-4 Hours). Learn more about merging in the wiki. Questions? Feedback? Please reach out to the PyTorch DevX Team |
AmdSampsa
pushed a commit
to AmdSampsa/pytorch
that referenced
this pull request
Dec 9, 2024
Today, when user does `init_process_group()`, without `backend` or `device_id` specification, we would auto-translate it into `cuda:nccl,cpu:gloo`. The idea was to initialize all **default** backends to cover what the user may do later. A side effect is increase of initialization time and resources. This PR changes it to detecting the accelerator type on the machine, and initialize only the backend for that accelerator. Pull Request resolved: pytorch#142216 Approved by: https://github.com/wconstab, https://github.com/XilunWu
kwen2501
added a commit
that referenced
this pull request
Dec 9, 2024
Update doc to reflect change brought by #142216 cc H-Huang awgu wanchaol fegin fduwjj wz337 wconstab d4l3k c-p-i-o [ghstack-poisoned]
kwen2501
added a commit
that referenced
this pull request
Dec 9, 2024
Update doc to reflect change brought by #142216 cc H-Huang awgu wanchaol fegin fduwjj wz337 wconstab d4l3k c-p-i-o [ghstack-poisoned]
pytorchmergebot
pushed a commit
that referenced
this pull request
Dec 9, 2024
Update doc to reflect change brought by #142216 Pull Request resolved: #142404 Approved by: https://github.com/XilunWu
pytorchmergebot
pushed a commit
that referenced
this pull request
Sep 6, 2025
inconsistent with the logic introduced in #162157 and modified in #142216.This update ensures the documentation matches the actual behavior of the code. Pull Request resolved: #162158 Approved by: https://github.com/wconstab
daisyden
pushed a commit
to daisyden/pytorch
that referenced
this pull request
Sep 8, 2025
inconsistent with the logic introduced in pytorch#162157 and modified in pytorch#142216.This update ensures the documentation matches the actual behavior of the code. Pull Request resolved: pytorch#162158 Approved by: https://github.com/wconstab
markc-614
pushed a commit
to markc-614/pytorch
that referenced
this pull request
Sep 17, 2025
inconsistent with the logic introduced in pytorch#162157 and modified in pytorch#142216.This update ensures the documentation matches the actual behavior of the code. Pull Request resolved: pytorch#162158 Approved by: https://github.com/wconstab
mansiag05
pushed a commit
to mansiag05/pytorch
that referenced
this pull request
Sep 22, 2025
inconsistent with the logic introduced in pytorch#162157 and modified in pytorch#142216.This update ensures the documentation matches the actual behavior of the code. Pull Request resolved: pytorch#162158 Approved by: https://github.com/wconstab
cleonard530
pushed a commit
to cleonard530/pytorch
that referenced
this pull request
Sep 22, 2025
inconsistent with the logic introduced in pytorch#162157 and modified in pytorch#142216.This update ensures the documentation matches the actual behavior of the code. Pull Request resolved: pytorch#162158 Approved by: https://github.com/wconstab
dsashidh
pushed a commit
to dsashidh/pytorch
that referenced
this pull request
Sep 26, 2025
inconsistent with the logic introduced in pytorch#162157 and modified in pytorch#142216.This update ensures the documentation matches the actual behavior of the code. Pull Request resolved: pytorch#162158 Approved by: https://github.com/wconstab
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Stack from ghstack (oldest at bottom):
Today, when user does
init_process_group(), withoutbackendordevice_idspecification, we would auto-translate it intocuda:nccl,cpu:gloo. The idea was to initialize all default backends to cover what the user may do later.A side effect is increase of initialization time and resources.
This PR changes it to detecting the accelerator type on the machine, and initialize only the backend for that accelerator.
cc @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o