Add support for linking counter y-axis with TrackEvent This change adds support for linking the y-axis of counter tracks in the Perfetto UI. This is useful when multiple counter tracks are related and should be displayed with the same y-axis range for easier comparison. The changes include: - Adding a `y_axis_share_key` field to the `CounterDescriptor` proto. - Propagating this key through the trace processor and adding it as a track argument. - Updating the UI to use this key to group tracks for y-axis sharing. The parent track ID is also included in the sharing key to ensure that only tracks under the same parent are linked. - Adding a diff test to verify the new feature. - Updating the documentation. Fixes #2461
Perfetto is an open-source suite of SDKs, daemons and tools which use tracing to help developers understand the behaviour of complex systems and root-cause functional and performance issues on client and embedded systems.
It is a production-grade tool that is the default tracing system for the Android operating system and the Chromium browser.
Perfetto is not a single tool, but a collection of components that work together:
Perfetto was designed to be a versatile and powerful tracing system for a wide range of use cases.
ftrace, allowing you to visualize scheduling, syscalls, interrupts, and custom kernel tracepoints on a timeline.chrome://tracing. Use it to debug and root-cause issues in the browser, V8, and Blink.We‘ve designed our documentation to guide you to the right information as quickly as possible, whether you’re a newcomer to performance analysis or an experienced developer.
New to tracing? If you're unfamiliar with concepts like tracing and profiling, start here:
Ready to dive in? Our “Getting Started” guide is the main entry point for all users. It will help you find the right tutorials and documentation for your specific needs:
Want the full overview? For a comprehensive look at what Perfetto is, why it's useful, and who uses it, see our main documentation page:
Have questions? Need help?
We follow Google's Open Source Community Guidelines.