tracing: Add init option to avoid linking system consumer

Today when using perfetto::Tracing::Initialize() with the system
backend, both the producer and the consumer side of the ipcs are linked
in, even though most perfetto users will not likely use the consumer
side.

The consumer side implementation is responsible for a large portion of
the statically linked binary size (~100Kbytes out of ~700kBytes, thanks
rzuklie@google.com for finding that out!).

This commit adds an option to perfetto::Tracing::Initialize to avoid
initializing the consumer side of the system backend.

Change-Id: I17a72f4864c6c300a6a734f93b349e6d020f1967
7 files changed
tree: 2b3372c7b6b11b5f24a0ba7dde8b5cca2476c169
  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. .git-blame-ignore-revs
  20. .gitattributes
  21. .gitignore
  22. .gn
  23. .style.yapf
  24. Android.bp
  25. Android.bp.extras
  26. BUILD
  27. BUILD.extras
  28. BUILD.gn
  29. CHANGELOG
  30. codereview.settings
  31. DIR_METADATA
  32. heapprofd.rc
  33. LICENSE
  34. meson.build
  35. METADATA
  36. MODULE_LICENSE_APACHE2
  37. OWNERS
  38. perfetto.rc
  39. PerfettoIntegrationTests.xml
  40. PRESUBMIT.py
  41. README.chromium
  42. README.md
  43. TEST_MAPPING
  44. traced_perf.rc
  45. 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.