Collect ftrace protos into one file per group

Rather than have one proto for each ftrace event have one per group.
This cuts ~800 build targets and reduces the time for a clean build by
~30%.

Before:
$ time ninja -C out/mac_debug/
[1881/1881] stamp obj/default.stamp
ninja -C out/mac_debug  1292.93s user 117.97s system 717% cpu 3:16.73 total

After:
$ time ninja -C out/mac_debug/
[1035/1035] stamp obj/default.stamp
ninja -C out/mac_debug/  895.71s user 71.32s system 745% cpu 2:09.70 total
Change-Id: Ieff7e8721b9d3b240db722105baf1651d4ac8bb5
335 files changed
tree: 8790e877e9b2d88f425ce016bf69b49c332c252c
  1. build_overrides/
  2. buildtools/
  3. debian/
  4. docs/
  5. gn/
  6. include/
  7. infra/
  8. protos/
  9. src/
  10. test/
  11. tools/
  12. ui/
  13. .clang-format
  14. .gitignore
  15. .gn
  16. .travis.yml
  17. Android.bp
  18. Android.bp.extras
  19. BUILD.gn
  20. codereview.settings
  21. heapprofd.rc
  22. MODULE_LICENSE_APACHE2
  23. NOTICE
  24. OWNERS
  25. perfetto.rc
  26. PRESUBMIT.py
  27. README.chromium
  28. README.md
README.md

Perfetto - Performance instrumentation and tracing

Perfetto is an open-source project for performance instrumentation and tracing of Linux/Android/Chrome platforms and user-space apps.

See www.perfetto.dev for docs.

Bugs

  • For bugs affecting Android or the tracing internals use the internal bug tracker (go/perfetto-bugs).
  • For bugs affecting Chrome use http://crbug.com, Component:Speed>Tracing label:Perfetto.