-
Notifications
You must be signed in to change notification settings - Fork 3
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
Episode: Function Level Profiling #6
Conversation
❌ DANGER ❌This pull request has modified workflows that created output. Close this now. |
08ca416
to
8b80523
Compare
b278308
to
ce92587
Compare
c34cd90
to
0fe739c
Compare
episodes/profiling-functions.md
Outdated
The third row represents `a_1()`, the only method called from global scope, therefore the first two rows represent Python's internal code for launching our script and can be ignored (by clicking on the third row). | ||
|
||
The row following `a_1()` is split into three boxes representing `b_1()`, `time.sleep()` and `b_2()` in the order they were first called. Note that `b_1()` is called three times, but only has one box within the icicle diagram. |
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.
in the order they were first called
This is correct for this example, but not in general.
It would appear they are ordered according to cumtime
, unhelpfully not shown on hover/click in the left-hand column.
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.
Had a play with this example and it doesn't clearly seem to be cumtime
, tottime
, or ncalls
. It's a mystery although it normally corresponds with tottime
.
ded5fe1
to
bd63eb6
Compare
Closes #3