Component used: Macrobenchmark Version used: 1.1.1 Devices/Android versions reproduced on: N/A, API Change Request
Currently, Macrobenchmark is focused on activities. Facilities should be added to address the benchmarking of at least the startup of other android components, notably Services and Broadcast Receivers.
A core macrobenchmark use case is profiling startup, and a significant part of that is application startup. However, the application startup pathway is not necessarily consistent between entry points. Profiling these cases is not directly supported by the library, which makes it difficult to get accurate results. In addition, the library as designed prevents profiling the startup or other lifecycle functionality of non-activity components themselves, which seems moderately important.
Description
Version used: 1.1.1
Devices/Android versions reproduced on: N/A, API Change Request
Currently, Macrobenchmark is focused on activities. Facilities should be added to address the benchmarking of at least the startup of other android components, notably Services and Broadcast Receivers.
A core macrobenchmark use case is profiling startup, and a significant part of that is application startup. However, the application startup pathway is not necessarily consistent between entry points. Profiling these cases is not directly supported by the library, which makes it difficult to get accurate results. In addition, the library as designed prevents profiling the startup or other lifecycle functionality of non-activity components themselves, which seems moderately important.