-
Notifications
You must be signed in to change notification settings - Fork 26.3k
[Profiler] Memory profiler part 13: Add sizes to timeline. #89356
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
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/89356
Note: Links to docs will display an error until the docs builds have been completed. ✅ No FailuresAs of commit cfae7c2: This comment was automatically generated by Dr. CI and updates every 15 minutes. |
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) ghstack-source-id: 174078158 Pull Request resolved: #89356
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
Pull Request resolved: #89356 If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. ghstack-source-id: 174223953 Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/)
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
Pull Request resolved: #89356 If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. ghstack-source-id: 174422769 Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/)
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
Pull Request resolved: #89356 If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. ghstack-source-id: 174633852 Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/)
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
Pull Request resolved: #89356 If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. ghstack-source-id: 174685527 Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/)
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
Pull Request resolved: #89356 If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. ghstack-source-id: 174760327 Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/)
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
Pull Request resolved: #89356 If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. ghstack-source-id: 174825887 Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/)
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) [ghstack-poisoned]
Pull Request resolved: #89356 If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. ghstack-source-id: 174868149 Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/)
|
@pytorchbot merge |
Merge failedReason: PR #89356 has not been reviewed yet (Rule superuser) 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 |
Merge failedReason: The following mandatory check(s) failed (Rule Dig deeper by viewing the failures on hud 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 |
…9356) If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage. Differential Revision: [D40868660](https://our.internmc.facebook.com/intern/diff/D40868660/) Pull Request resolved: pytorch#89356 Approved by: https://github.com/chaekit
Stack from ghstack (oldest at bottom):
If we see an allocation the size is unambiguous. Otherwise we have to use sizes and strides to bound the underlying storage.
Differential Revision: D40868660