commit | f7668fd47eba3b08043eca47fb7080a86727af49 | [log] [tgz] |
---|---|---|
author | Primiano Tucci <primiano@google.com> | Thu Aug 29 14:16:06 2024 +0100 |
committer | Primiano Tucci <primiano@google.com> | Thu Aug 29 14:16:06 2024 +0100 |
tree | 5603bcb0de84b2dceaa90c1896f166e961c67f70 | |
parent | d008686ccd7cae015fdea0c85fcfae69a637c995 [diff] |
Simplify further TrackManager, get rid of TrackBundle Have only one container owning track and get rid of trackCache. I always found the notion of "Track cache" a very odd concept. The caching is an implementation detail on how we swap in/out lifecycle methods to save resources in TP. It should not leak to the outside. Anybody else outisde should only reason about Tracks, nobody should worry about the internal caching behaviour. Change-Id: I1d4651ad5b91896b85e0e7771f19060da4e7afe6
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.