-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
[Debugger] Sorting op-time breakdown for quicker analysis. #4352
Conversation
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.
LGTM
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.
LGTM
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.
Awesome, thanks lot for the change. LGTM.
BTW, if I remember correctly, the correct output is sorted by the occurrence of the ops. If so, should we make this configurable, i.e. passing a |
accb4d3
to
9e1929f
Compare
@zhiics Makes sense. Added a flag. |
9e1929f
to
59d2c6c
Compare
Thanks @anijain2305 @icemelon9 @soiferj |
Profiler output is not sorted by time currently. So, a developer has to eyeball and find out the expensive ops. This PR sorts and add total time in the log for quicker analysis.
@tqchen @soiferj @yzhliu @icemelon9