Google Git
Sign in
fuchsia/third_party/github.com/google/perfetto/8f4cee14558f63f0d1888eab088d1266eb877f6d
commit
8f4cee14558f63f0d1888eab088d1266eb877f6d
[log]
author
Lalit Maganti <lalitm@google.com>
Wed Jul 02 18:40:38 2025 +0100
committer
GitHub <noreply@github.com>
Wed Jul 02 18:40:38 2025 +0100
tree
5e0475865ca18e666d790d9ef297b44e6891c2ba
parent
10b2f9e9df4e46f455eb3c9c4b0a037a7b1d78b7 [diff]
tp: don't require single sequence emission for incremental counter tracks (#2002)

We were forcing incremental counter tracks to come from the same
sequence as incrementality does not make sense across sequences.
However, it's perfectly legit for two threads to have their own view of
the same counter: for example for thread timestamps.

This happens in practice when multiple libraries are independently using
the sdk and enabling chrome timestamps (e.g. webview + cronet).

Fix this by allowing for multiple sequences to contribute to the same
track with independent incremental values.
10 files changed
tree: 5e0475865ca18e666d790d9ef297b44e6891c2ba
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. python/
  13. src/
  14. test/
  15. third_party/
  16. tools/
  17. ui/
  18. .bazelignore
  19. .bazelrc
  20. .bazelversion
  21. .clang-format
  22. .clang-tidy
  23. .git-blame-ignore-revs
  24. .gitallowed
  25. .gitattributes
  26. .gitignore
  27. .gn
  28. .style.yapf
  29. Android.bp
  30. Android.bp.extras
  31. BUILD
  32. BUILD.extras
  33. BUILD.gn
  34. CHANGELOG
  35. codereview.settings
  36. DIR_METADATA
  37. heapprofd.rc
  38. LICENSE
  39. meson.build
  40. METADATA
  41. MODULE.bazel
  42. MODULE.bazel.lock
  43. MODULE_LICENSE_APACHE2
  44. OWNERS
  45. perfetto.rc
  46. perfetto_flags.aconfig
  47. PerfettoIntegrationTests.xml
  48. persistent_cfg.pbtxt
  49. README.chromium
  50. README.md
  51. TEST_MAPPING
  52. traced_perf.rc
  53. WATCHLISTS
  54. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

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.

Core Components

Perfetto is not a single tool, but a collection of components that work together:

  • High-performance tracing daemons: For capturing tracing information from many processes on a single machine into a unified trace file.
  • Low-overhead tracing SDK: A C++17 library for direct userspace-to-userspace tracing of timings and state changes in your application.
  • Extensive OS-level probes: For capturing system-wide context on Android and Linux (e.g. scheduling states, CPU frequencies, memory profiling, callstack sampling).
  • Browser-based UI: A powerful, fully local UI for visualizing and exploring large, multi-GB traces on a timeline. It works in all major browsers, requires no installation, and can open traces from other tools.
  • SQL-based analysis library: A powerful engine that allows you to programmatically query traces using SQL to automate analysis and extract custom metrics.

Why Use Perfetto?

Perfetto was designed to be a versatile and powerful tracing system for a wide range of use cases.

  • For Android App & Platform Developers: Debug and root-cause functional and performance issues like slow startups, dropped frames (jank), animation glitches, low memory kills, and ANRs. Profile both Java/Kotlin and native C++ memory usage with heap dumps and profiles.
  • For C/C++ Developers (Linux, macOS, Windows): Use the Tracing SDK to instrument your application with custom trace points to understand its execution flow, find performance bottlenecks, and debug complex behavior. On Linux, you can also perform detailed CPU and native heap profiling.
  • For Linux Kernel & System Developers: Get deep insights into kernel behavior. Perfetto acts as an efficient userspace daemon for ftrace, allowing you to visualize scheduling, syscalls, interrupts, and custom kernel tracepoints on a timeline.
  • For Chromium Developers: Perfetto is the tracing backend for chrome://tracing. Use it to debug and root-cause issues in the browser, V8, and Blink.
  • For Performance Engineers & SREs: Analyze and visualize a wide range of profiling and tracing formats, not just Perfetto's. Use the powerful SQL interface to programmatically analyze traces from tools like Linux perf, macOS Instruments, Chrome JSON traces, and more.

Getting Started

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.

  1. New to tracing? If you're unfamiliar with concepts like tracing and profiling, start here:

  2. 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:

  3. 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:

Community & Support

Have questions? Need help?

We follow Google's Open Source Community Guidelines.