Skip to content
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

Trim flame graph nodes relative to node's parent #2815

Merged
merged 6 commits into from
Mar 21, 2023
Merged

Conversation

metalmatze
Copy link
Member

So far we have trimmed nodes based on the flame graph's absolute cumulative value. This is not what we want to do, given we might lose data when diving further into a flame graph.
However, in relation to the parent's cumulative value, there may occasion where the direct child still has too few values and would never be rendered. Those we want to trim.

cc @manojVivek @brancz

@metalmatze
Copy link
Member Author

Probably a good follow-up. We show the percentage of trimmed values. However, with these changes, they are often below 1%. I've seen trimmed values make up from 0.3% to 0.8%. Looking at the implementation in the frontend, we use new Intl.NumberFormat('en-US'); which doesn't support toFixed(2).
cc @manojVivek
Screenshot from 2023-03-21 16-52-21

So far we have trimmed nodes based on the absolute cumulative value. This is not what we want to do, given we might lose data when diving further into a flame graph.
However, in relation to the parent's cumulative value, there may occasion where the direct child still has to few values and would never be rendered. Those we want to trim.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants