Extract long binder transactions during app startups.

The transactions are considered long if they are longer 100ms. We can probably refine this threshold later if we need to.

We output all long transactions individually. Based on a bit of ad-hoc analysis, the cardinality isn't generally very high, and if it is, we would really want to know about it.

For each transaction, we output the duration and the thread, which (sometimes) gives some idea on what kind of binder call it was. I haven't yet figured out a better way to trace binder transactions from traces, so will probably refine this in the future.

Change-Id: I31be44b40cabec56ad728cc3e3086dc82265da56
5 files changed
tree: 40dddf02f58ba24b2c7192b7b00941fc535a2699
  1. .github/
  2. bazel/
  3. build_overrides/
  4. buildtools/
  5. debian/
  6. docs/
  7. examples/
  8. gn/
  9. include/
  10. infra/
  11. protos/
  12. src/
  13. test/
  14. tools/
  15. ui/
  16. .clang-format
  17. .clang-tidy
  18. .gitattributes
  19. .gitignore
  20. .gn
  21. .style.yapf
  22. Android.bp
  23. Android.bp.extras
  24. BUILD
  25. BUILD.extras
  26. BUILD.gn
  27. CHANGELOG
  28. codereview.settings
  29. DIR_METADATA
  30. heapprofd.rc
  31. LICENSE
  32. meson.build
  33. METADATA
  34. MODULE_LICENSE_APACHE2
  35. OWNERS
  36. perfetto.rc
  37. PerfettoIntegrationTests.xml
  38. PRESUBMIT.py
  39. README.chromium
  40. README.md
  41. TEST_MAPPING
  42. traced_perf.rc
  43. WORKSPACE
README.md

Perfetto - System profiling, app tracing and trace analysis

Perfetto is a production-grade open-source stack for performance instrumentation and trace analysis. It offers services and libraries and for recording system-level and app-level traces, native + java heap profiling, a library for analyzing traces using SQL and a web-based UI to visualize and explore multi-GB traces.

See https://perfetto.dev/docs or the /docs/ directory for documentation.