Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
[Profiling] Adding normalize by time and scale factor on Diff TopN functions page #159394
[Profiling] Adding normalize by time and scale factor on Diff TopN functions page #159394
Changes from 6 commits
9927c52
9cf53b9
b13e3d8
b667deb
c4b4f76
f7ec129
c6e840d
3777f35
93c9885
3593f54
dd9aed7
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Question: I'm not sure if I should scale the CPU values too! @elastic/profiling-ui does anybody know it?
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.
My understanding is that scaling the CPU values would require scaling both the numerator and denominator, which would cancel out the scaling factor when dividing. So I don't believe it's necessary.
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.
To show my work and prove it to myself also, here's my reasoning:
Without scaling
CPUdiff = 100 * (CPU1 / Total1) - 100 * (CPU2 / Total2)
or
CPUdiff = 100 * [(CPU1 / Total1) - (CPU2 / Total2)]
With scaling
CPUdiff = 100 * [(SF1* CPU1) / (SF1 * Total1)] - 100 * [(SF2 * CPU2) / (SF2 * Total2)]
or this after cancellation:
CPUdiff = 100 * (CPU1 / Total1) - 100 * (CPU2 / Total2)
which is the same as without scaling.
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.
TIL
wow, great explanation! thank you! 🤓