-
Notifications
You must be signed in to change notification settings - Fork 607
Fix memory profiling for memory.view ops #7925
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
Fix memory profiling for memory.view ops #7925
Conversation
ATT Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) [ghstack-poisoned]
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/7925
Note: Links to docs will display an error until the docs builds have been completed. ✅ You can merge normally! (1 Unrelated Failure)As of commit c6e2441 with merge base d4a8f8f ( BROKEN TRUNK - The following job failed but were 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. |
This pull request was exported from Phabricator. Differential Revision: D68448333 |
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.
Accepted internally, mirroring stamp
ATT Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) cc Olivia-liu Jack-Khuu [ghstack-poisoned]
This pull request was exported from Phabricator. Differential Revision: D68448333 |
ATT Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) cc Olivia-liu Jack-Khuu [ghstack-poisoned]
This pull request was exported from Phabricator. Differential Revision: D68448333 |
4168f93
into
gh/kimishpatel/150/base
Pull Request resolved: #7925 ATT ghstack-source-id: 263342054 @exported-using-ghexport Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) Co-authored-by: Kimish Patel <[email protected]>
* Fix memory profiling for memory.view ops Pull Request resolved: #7925 ATT ghstack-source-id: 263342054 @exported-using-ghexport Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) * [ET][Memory planning] Improve greedy memory planning. Pull Request resolved: #7926 This diff replaces the old greedy algorithm. Older algorithm resulted in 35% worse compared to theoretical optimum. THis matter for long context even more since additional overhead can be few hundred MB. For example the theorical optimial for llama3_2 8B, 4-bit quantized modelw ith context length of 2k needs about 1G of memory. This theoretcial max can be observed by looking at the peaks in memory profile. Current agorithm resulted in about 1.6GB of planned memory. New algorithm reduce that to about 1.1G. ghstack-source-id: 263342052 @exported-using-ghexport Differential Revision: [D68448332](https://our.internmc.facebook.com/intern/diff/D68448332/) --------- Co-authored-by: Kimish Patel <[email protected]>
Pull Request resolved: #7925 ATT ghstack-source-id: 263342054 @exported-using-ghexport Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) Co-authored-by: Kimish Patel <[email protected]>
* Fix memory profiling for memory.view ops Pull Request resolved: #7925 ATT ghstack-source-id: 263342054 @exported-using-ghexport Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) * [ET][Memory planning] Improve greedy memory planning. Pull Request resolved: #7926 This diff replaces the old greedy algorithm. Older algorithm resulted in 35% worse compared to theoretical optimum. THis matter for long context even more since additional overhead can be few hundred MB. For example the theorical optimial for llama3_2 8B, 4-bit quantized modelw ith context length of 2k needs about 1G of memory. This theoretcial max can be observed by looking at the peaks in memory profile. Current agorithm resulted in about 1.6GB of planned memory. New algorithm reduce that to about 1.1G. ghstack-source-id: 263342052 @exported-using-ghexport Differential Revision: [D68448332](https://our.internmc.facebook.com/intern/diff/D68448332/) --------- Co-authored-by: Kimish Patel <[email protected]>
Pull Request resolved: pytorch#7925 ATT ghstack-source-id: 263342054 @exported-using-ghexport Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) Co-authored-by: Kimish Patel <[email protected]>
* Fix memory profiling for memory.view ops Pull Request resolved: pytorch#7925 ATT ghstack-source-id: 263342054 @exported-using-ghexport Differential Revision: [D68448333](https://our.internmc.facebook.com/intern/diff/D68448333/) * [ET][Memory planning] Improve greedy memory planning. Pull Request resolved: pytorch#7926 This diff replaces the old greedy algorithm. Older algorithm resulted in 35% worse compared to theoretical optimum. THis matter for long context even more since additional overhead can be few hundred MB. For example the theorical optimial for llama3_2 8B, 4-bit quantized modelw ith context length of 2k needs about 1G of memory. This theoretcial max can be observed by looking at the peaks in memory profile. Current agorithm resulted in about 1.6GB of planned memory. New algorithm reduce that to about 1.1G. ghstack-source-id: 263342052 @exported-using-ghexport Differential Revision: [D68448332](https://our.internmc.facebook.com/intern/diff/D68448332/) --------- Co-authored-by: Kimish Patel <[email protected]>
Stack from ghstack (oldest at bottom):
ATT
Differential Revision: D68448333
cc @Olivia-liu @Jack-Khuu