| commit | c8ae6935b8a66edbc988339d39ed3b76863e6d53 | [log] [tgz] |
|---|---|---|
| author | Priyanka <57577698+PriyankaSPX@users.noreply.github.com> | Mon Jul 07 18:44:42 2025 +0100 |
| committer | GitHub <noreply@github.com> | Mon Jul 07 18:44:42 2025 +0100 |
| tree | e50ae1bcc74d988274a3544c1346561062c7dd40 | |
| parent | a0e89bb4eaeb53ff97843d4eedbaf02952305b52 [diff] |
tp: SF visibility computation unit tests (#2052) Unit test SF visibility computation. Bug: 411363817 Test: tools/ninja -C out/linux_clang_release perfetto_unittests && out/linux_clang_release/perfetto_unittests --gtest_filter=SfVisibilityComputation*
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.