| commit | ece03501a9dc916c2ee8ff1bb6fef62e0f0febd0 | [log] [tgz] |
|---|---|---|
| author | Deepanjan Roy <dproy@google.com> | Wed Aug 05 15:47:16 2020 -0400 |
| committer | Deepanjan Roy <dproy@google.com> | Wed Aug 05 15:47:16 2020 -0400 |
| tree | f097c693fd110e506dea14912955d7d76cd13f02 | |
| parent | 9a43f48ed4cd22ec0f6e1436cd88b829a3b99550 [diff] |
[metrics] Change the example chrome metric to not clash with chromium Since we have not implemented a good way to shadow proto and sql files between what's loaded in memory (proto and sql files checked into perfetto) and what's loaded at runtime (proto and sql files checked into chromium/src/.../tbmv3), having duplicate metrics can lead to a lot of trouble. In particular, it will stop working if we enforce single definition of messages as in https://r.android.com/1386237. The libprotobuf descriptor pool in trace_processor_shell already rejects the runtime-loaded definition of console_error_metric, so this can lead to many subtle bugs. We will have a proper virtual file system with well defined shadowing soon, and then this test chrome metric will go away to be replaced with all metrics rolled in from chromium. Bug: 161697620 Change-Id: Iede9af8a04d4e352c0323b36e698ee6805de2cab
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.