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
reduce computation of batch_norm when weight or bias is none #104616
Conversation
[ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/104616
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit 1cf15bb: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
ghstack-source-id: 2c520610c4e0daaddb35b1f979992058c4f937d6 Pull Request resolved: #104616
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.
Nice catch!
@pytorchbot merge |
Merge failedReason: This PR needs a If not, please add the To add a label, you can comment to pytorchbot, for example For more information, see Details for Dev Infra teamRaised by workflow job |
@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 |
Stack from ghstack (oldest at bottom):
For batch_norm decomposition, if weight or bias is None, we can skip some computations for better performance.