commit | 2b438fed45d9aea443f3b6a8f062d7bc1402a361 | [log] [tgz] |
---|---|---|
author | Aurimas Liutikas <aurimas@google.com> | Wed May 12 21:56:38 2021 +0000 |
committer | android-build-team Robot <android-build-team-robot@google.com> | Wed May 12 22:21:29 2021 +0000 |
tree | c46c4554991f543a715def82541c27f3db50e393 | |
parent | cde79a11f3b0a07982368036364a7b47f7ae4397 [diff] |
Revert "Fix usage of minBy to unblock Kotlin 1.5 upgrade" This reverts commit 6e914b3fe586f61c24e5add5e903a375be94f756. Reason for revert: b/187908823 Change-Id: I12da9f0984d68b8335ff88c83b5a721c0922495d (cherry picked from commit 375f839d08f42cde0da7d623a44d0d082610662d)
Trebuchet is a Kotlin library for parsing and analyzing Android trace files generated by the atrace
or systrace
commands. This is not an officially supported Google product.
The code for the Trebuchet library can be found in the core/
directory.
Trebuchet comes bundled with several programs for analyzing one or more trace files.
The Startup Analyzer program takes a trace file, detects any startup events that occurred during the traced time period, and prints information about the events. If Trebuchet is built using the Android build system, there will be a StartupAnalyzerKt program placed into a directory that is a member of the PATH system variable. If you wish to use Gradle, you can use the startup-analyzer.sh
script located in the scripts/
directory.
The Startup Summarizer program takes a set of trace files, detects startup events in each file, and computes average and standard deviation for startup stats, broken down by program name, compiler filter, and cache status. If Trebuchet is built using the Android build system, there will be a StartupSummarizerKt program placed into a directory that is a member of the PATH system variable. If you wish to use Gradle, you can use the startup-summarizer.sh
script located in the scripts/
directory.
The scripts/
directory contains a shell script called run-startup.sh
, which will start a trace, launch an activity given a package name and an activity name, transfer the trace file to the host machine, and run the StartupAnalyzer.