-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[BE][Ez]: Fix docs recommending inefficient tensor op order #144270
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
[BE][Ez]: Fix docs recommending inefficient tensor op order #144270
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/144270
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (2 Unrelated Failures)As of commit 91cfdbd with merge base f6488d8 ( FLAKY - The following job failed but was likely due to flakiness present on trunk:
BROKEN TRUNK - The following job failed but was present on the merge base:👉 Rebase onto the `viable/strict` branch to avoid these failures
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
f37b6ae to
e6f98a9
Compare
e6f98a9 to
91cfdbd
Compare
awgu
left a comment
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.
This looks reasonable to me!
|
Maybe we can add similar changes to |
|
@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 |
…44469) Follow up to #144270 and fix some vulkan code Pull Request resolved: #144469 Approved by: https://github.com/awgu
detach().clone()is faster than.clone().detatch()since the gradients are not cloned. Let's update all the documentation and tests so that users do not use the inefficient op ordering.