Skip to content

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

Merged
merged 3 commits into from
Jan 28, 2025

Conversation

kimishpatel
Copy link
Contributor

@kimishpatel kimishpatel commented Jan 24, 2025

Copy link

pytorch-bot bot commented Jan 24, 2025

🔗 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 (image):

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.

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Jan 24, 2025
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D68448333

@kimishpatel kimishpatel added module: devtools Issues related to developer tools and code under devtools/ release notes: devtools Changes to dev tooling, for example the debugger & profiler labels Jan 24, 2025
Copy link
Contributor

@Jack-Khuu Jack-Khuu left a 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]
@facebook-github-bot
Copy link
Contributor

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]
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D68448333

@facebook-github-bot facebook-github-bot merged commit 4168f93 into gh/kimishpatel/150/base Jan 28, 2025
45 of 47 checks passed
@facebook-github-bot facebook-github-bot deleted the gh/kimishpatel/150/head branch January 28, 2025 05:28
swolchok pushed a commit that referenced this pull request Jan 28, 2025
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]>
manuelcandales pushed a commit that referenced this pull request Jan 28, 2025
* 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]>
YIWENX14 pushed a commit that referenced this pull request Jan 28, 2025
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]>
YIWENX14 pushed a commit that referenced this pull request Jan 28, 2025
* 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]>
zonglinpeng pushed a commit to zonglinpeng/executorch that referenced this pull request Jan 30, 2025
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]>
zonglinpeng pushed a commit to zonglinpeng/executorch that referenced this pull request Jan 30, 2025
* 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported module: devtools Issues related to developer tools and code under devtools/ release notes: devtools Changes to dev tooling, for example the debugger & profiler
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants