-
Notifications
You must be signed in to change notification settings - Fork 646
[Profiling] Add python scripts to generate per-op profiling from etdumps #13302
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
base: main
Are you sure you want to change the base?
Conversation
🔗 Helpful Links🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/13302
Note: Links to docs will display an error until the docs builds have been completed. ❌ 4 New FailuresAs of commit 55d189a with merge base a84b3c9 ( NEW FAILURES - The following jobs have failed:
This comment was automatically generated by Dr. CI and updates every 15 minutes. |
LGTM. Thanks for adding scripts! Please add some comments and/or a .md file demonstrating how to use your script |
Hi @mcr229! Thank you for your pull request. We require contributors to sign our Contributor License Agreement, and yours needs attention. You currently have a record in our system, but the CLA is no longer valid, and will need to be resubmitted. ProcessIn order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA. Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with If you have received this in error or have any questions, please contact us at [email protected]. Thanks! |
I've been doing a lot of profiling out in open source, and that generally involves generating an etdump after running the model. I find this script very useful for generating a CSV of the per-op profiling numbers after getting an etdump. Currently the profiling flow looks like this for me:
This generates some nice CSVs for investigating the per-op profiling times. See some of the commits in this stack for profiling info.