diff options
| author | Nataniel Borges <natanieljr@google.com> | 2019-02-01 14:45:55 -0800 |
|---|---|---|
| committer | Nataniel Borges <natanieljr@google.com> | 2019-02-08 10:13:38 -0800 |
| commit | 48d9aa96b1b61a94118a9bece28cdf39b70c7124 (patch) | |
| tree | fc339d7395ccae4991d13cc3c3085024a6832542 /tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp | |
| parent | 580a7429e10a721e9dcf4bab818cb9214ef5b299 (diff) | |
Log window trace data per frame in continuous mode
When using non-continuous mode the WM Service logs each transaction
applied. This is incur in performance loss.
For continuous mode we need a more efficient mechanism to log the data,
thus we log only 1x per frame and only if a transaction has been
applied.
Test: Flash a device. Enable the continuous mode for tracing using
`adb shell cmd window tracing continuous true` and start the trace with
`adb shell cmd window tracing start`. Use the device. To stop the trace
and log the data to disk use `adb shell cmd window tracing stop`. Open
the trace in Winscope and check if all `entry` elements have the
following property: `where: onFrame`
Change-Id: I1034d9e1b7b8a105d4e16a1aeb4b7341fff5f157
Diffstat (limited to 'tests/DynamicCodeLoggerIntegrationTests/src/cpp/test_executable.cpp')
0 files changed, 0 insertions, 0 deletions