-
Notifications
You must be signed in to change notification settings - Fork 230
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
ui: Improve showing filtered and trimmed nodes in ProfileIcicleGraph #2758
Conversation
Oh, seems like #2756 created a merge conflict. I'll rebase these tomorrow. Other follow-ups are:
|
Super cool!! I think the indicating text should be above the icicle graph as it's unpredictable how large it may be so you may not even know if that text is there just because the icicle graph is too tall. |
ca9755c
to
2ae59ba
Compare
It was there before and I moved it below the graph. It's mostly debugging information that's there when needed but nothing that usually concerns users unless they look for it. |
I'm writing and updating the flamegraph_table_test.go cases now. 😌 |
Alright happy with trying like this. I'm not convinced if I'm honest but I was wrong about function filtering as well, so I'm very happy to give it a shot and build an opinion again after using it a bit. |
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!
4eed7ec
to
aa960f5
Compare
ui/ProfileIcicleGraph: Improve wording for trimmed samples
Deprecate the total values on the individual report types.
b6ca6db
to
3abd7c6
Compare
If nothing gets filtered and trimmed the icicle graph now looks like this (see the line at the bottom).

With trimming enabled:

With filtering by function (for

sort
)And finally with both trimming and filtering.
