platform_system_core/bootstat
Tej Singh 993f65619e Fix performance degradation from BootSequence atom
(partial cherry pick from commit fe3e762b6d)

Adding the boot sequence reported atom in ag/3518079 caused the duration
of bootstat to increase, as seen in b/72864061. I isolated the cause
down to calling BootReasonStrToReason. However, this function also gets
called in ReportBootReason, so I created another function that does the
parsing and sets the system boot reason property, and made
RecordBootReason and statsd logging get that property.

Bug: 72864061
Test: rebooted phone, verified boot events were received in adb shell
logcat -b stats and verified adb shell bootstat -p printed correct
values. Ran timing tests as well on walleye with 20 boots: before this
change, the average was ~150-160ms. After, it was ~80ms.
Change-Id: I92dbc9880328835647be7d9d50c7861b42f27bdb
Merged-In: I92dbc9880328835647be7d9d50c7861b42f27bdb
2018-06-04 13:31:05 -07:00
..
.clang-format bootstat: Set up clang-format-2 for bootstat. 2017-05-24 10:19:25 -07:00
Android.bp Fix PDK build 2018-02-14 03:03:28 +00:00
AndroidTest.xml Add test config to bootstat_tests 2017-04-05 14:49:47 +00:00
boot_event_record_store.cpp bootstat: clang-format rebase 2017-09-20 11:27:56 -07:00
boot_event_record_store.h bootstat: clang-format rebase 2017-09-20 11:27:56 -07:00
boot_event_record_store_test.cpp bootstat: clang-format rebase 2017-09-20 11:27:56 -07:00
boot_reason_test.sh bootstat: refine boot reasons 2018-06-04 08:32:23 -07:00
bootstat-debug.rc bootstat: test: inject ro.boot.bootreason values 2017-10-11 13:48:33 -07:00
bootstat.cpp Fix performance degradation from BootSequence atom 2018-06-04 13:31:05 -07:00
bootstat.rc Fix performance degradation from BootSequence atom 2018-06-04 13:31:05 -07:00
OWNERS Add OWNERS. 2017-12-07 13:30:03 -08:00
README.md bootstat: Record the time since factory reset on init. 2016-02-24 11:01:03 -08:00
testrunner.cpp bootstat: Fix the base includes to be AOSP-friendly. 2016-01-20 01:28:48 +00:00

bootstat

The bootstat command records boot events (e.g., firmware_loaded, boot_complete) and the relative time at which these events occurred. The command also aggregates boot event metrics locally and logs the metrics for analysis.

Usage: bootstat [options]
options include:
  -h, --help            Show this help
  -l, --log             Log all metrics to logstorage
  -p, --print           Dump the boot event records to the console
  -r, --record          Record the timestamp of a named boot event
  --record_boot_reason  Record the reason why the device booted
  --record_time_since_factory_reset Record the time since the device was reset

Relative time

The timestamp recorded by bootstat is the uptime of the system, i.e., the number of seconds since the system booted.

Recording boot events

To record the relative time of an event during the boot phase, call bootstat with the -r option and the name of the boot event.

$ bootstat -r boot_complete

The relative time at which the command runs is recorded along with the name of the boot event to be persisted.

Logging boot events

To log the persisted boot events, call bootstat with the -l option.

$ bootstat -l

bootstat logs all boot events recorded using the -r option to the EventLog using the Tron histogram. These logs may be uploaded by interested parties for aggregation and analysis of boot time across different devices and versions.

Printing boot events

To print the set of persisted boot events, call bootstat with the -p option.

$ bootstat -p
Boot events:
------------
boot_complete   71