-
Notifications
You must be signed in to change notification settings - Fork 25.7k
[pipelining] Fix 'last backward' counting for dI / dW #139415
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/139415
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 1a9edfe with merge base failed to retrieve merge base, please contact dev infra: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for cleaning this up
|
@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 |
Cleaning up counters / extra variables not needed after #139415 was landed Pull Request resolved: #139817 Approved by: https://github.com/wconstab
Cleaning up counters / extra variables not needed after pytorch#139415 was landed Pull Request resolved: pytorch#139817 Approved by: https://github.com/wconstab
Stack from ghstack (oldest at bottom):
Since any stage can run a mixture of full backwards and split backwards,
it is important to count the sum of (full_backwards + backward_weight)
when comparing to num microbatches to determine last backward.
cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @d4l3k @c-p-i-o