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

bug: ProcessSummaryTrack UI is limited to top level process tracks #1020

Open
dreveman opened this issue Feb 20, 2025 · 3 comments
Open

bug: ProcessSummaryTrack UI is limited to top level process tracks #1020

dreveman opened this issue Feb 20, 2025 · 3 comments

Comments

@dreveman
Copy link

With the addition of arbitrarily nested process tracks it would be nice to have all summary tracks support summarization of child tracks even if they don't represent system threads.

@LalitMaganti wdyt?

@LalitMaganti
Copy link
Collaborator

Generally in agreement but unclear to me how this would actually work in practice.

@dreveman
Copy link
Author

I've only been thinking about at the higher level of what's exposed in the UI but will take a look at how it can be implemented next as we're in agreement that it would be a useful.

@mohammadawwad
Copy link

the plugin dev.perfetto.ProcessSummary provides a structured approach for handling nested process summaries by using virtual tables (__intrinsic_counter_mipmap), SQL-based transformations, and TimelineFetcher to dynamically request data. It aggregates thread slices and computes process-level utilization but is limited to main process-based tracks. A similar approach could be beneficial for counter-based tracks, allowing for nested counter summaries that aggregate values across multiple track IDs. Implementing a dev.perfetto.CounterSummary plugin or extending the functionality to nested tracks could help improve counter visualization within large traces and providing hierarchical counter groupings.

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

No branches or pull requests

3 participants