Improve clustering of restricted_location for mojo pipes.

Currently mojo pipes have three different paths to call a mojo
interface, however when attributing jank we don't really worry about the
mojo path, but rather who triggered mojo to execute. So modify mojo
based names to group them into one for attribution.

Also we expose avg_vsync_interval so that when we are computing sums
over the data we can filter out events less then avg_vsync_interval
since we've found that they can be very frequent. However we don't just
filter them out in this metric because this metric is the ground truth
and our tagging query adds conditions about what we car about.

Bug: 209448519
Change-Id: I964ef1a3fd1c6b7b9b713d647e59190ecdc07445
5 files changed
tree: 3990a8a1053fd9818120b786810ffae22ca9e64a
  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. tools/
  16. ui/
  17. .clang-format
  18. .clang-tidy
  19. .gitattributes
  20. .gitignore
  21. .gn
  22. .style.yapf
  23. Android.bp
  24. Android.bp.extras
  25. BUILD
  26. BUILD.extras
  27. BUILD.gn
  28. CHANGELOG
  29. codereview.settings
  30. DIR_METADATA
  31. heapprofd.rc
  32. LICENSE
  33. meson.build
  34. METADATA
  35. MODULE_LICENSE_APACHE2
  36. OWNERS
  37. perfetto.rc
  38. PerfettoIntegrationTests.xml
  39. PRESUBMIT.py
  40. README.chromium
  41. README.md
  42. TEST_MAPPING
  43. traced_perf.rc
  44. 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.