KEMBAR78
Add wait counter for nccl abort by atuljangra · Pull Request #136067 · pytorch/pytorch · GitHub
Skip to content

Conversation

@atuljangra
Copy link
Contributor

@atuljangra atuljangra commented Sep 14, 2024

Summary:
Quite a few times, we see the NCCL PG abort taking too long. There's no easy way to measure this, so let's add a counter to measure this across the stack.

This will help us measure how much time we take the NCCL abort.
Test Plan:
Unit tests

Reviewed By: c-p-i-o

Differential Revision: D62675010

cc @XilunWu @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o

@pytorch-bot
Copy link

pytorch-bot bot commented Sep 14, 2024

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/136067

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 75445cc with merge base 48d18fb (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@pytorch-bot pytorch-bot bot added oncall: distributed Add this issue/PR to distributed oncall triage queue release notes: distributed (c10d) release notes category labels Sep 14, 2024
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D62675010

@pytorch-bot pytorch-bot bot added the ciflow/trunk Trigger trunk jobs on your pull request label Sep 14, 2024
@kwen2501
Copy link
Contributor

@atuljangra do you mind adding a brief comment above the code describing what the code does?
Our PR description would be a perfect fit.
Thanks!

@atuljangra
Copy link
Contributor Author

@kwen2501 Added some more details int eh description.

@kwen2501
Copy link
Contributor

@atuljangra Thanks. Maybe I confused you :) What I meant was to copy the PR description into the code as a comment (so that readers know what that line of code is for).

@atuljangra
Copy link
Contributor Author

@kwen2501 Ah got it, will update.

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D62675010

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D62675010

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D62675010

@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D62675010

Summary:
Pull Request resolved: pytorch#136067

Quite a few times, we see the NCCL PG abort taking too long. There's no easy way to measure this, so let's add a counter to measure this across the stack.

Example job where this would have been useful: f641288746-TrainingApplication

Test Plan:
Unit tests

https://www.internalfb.com/mlhub/pipelines/runs/mast/aps-atuljangra-8519d57d57?job_attempt=0&env=PRODUCTION

Reviewed By: c-p-i-o

Differential Revision: D62675010
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D62675010

@facebook-github-bot
Copy link
Contributor

@pytorchbot merge -f 'Landed internally'

(Initiating merge automatically since Phabricator Diff has merged, using force because this PR might not pass merge_rules.json but landed internally)

@pytorchmergebot
Copy link
Collaborator

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes). Please use -f as last resort and instead consider -i/--ignore-current to continue the merge ignoring current failures. This will allow currently pending tests to finish and report signal before the merge.

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging
Check the merge workflow status
here

Chao1Han pushed a commit to Chao1Han/pytorch that referenced this pull request Sep 20, 2024
Summary:
Quite a few times, we see the NCCL PG abort taking too long. There's no easy way to measure this, so let's add a counter to measure this across the stack.

This will help us measure how much time we take the NCCL abort.
Test Plan:
Unit tests

Reviewed By: c-p-i-o

Differential Revision: D62675010

Pull Request resolved: pytorch#136067
Approved by: https://github.com/fduwjj
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

ciflow/trunk Trigger trunk jobs on your pull request fb-exported Merged oncall: distributed Add this issue/PR to distributed oncall triage queue release notes: distributed (c10d) release notes category

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants