forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improve battor_agent interactive mode
The battor_agent StopTracing command, if no file name is specified, printed the raw sampling data which can easily be 100,000 lines of numbers. This is not helpful. This change improves this case, especially when in interactive mode. Now a BattorResults object is returned which contains a detailed string representation of the results and enough information to allow creating a summary. When in battor_agent's interactive mode the summary is printed and the details are saved to a file (using a generated file name if none is supplied). The summary result format is for human consumption and is subject to change but currently it looks like this: StopTracing Second 0 average power: 9.20 W Second 1 average power: 8.65 W Second 2 average power: 11.38 W Average power over 3.14 s : 9.74 W Summary of power-by-seconds: Minimum: 8.65 Median: 9.20 Maximum: 11.38 Saving detailed results to c:\users\brucedawson\desktop\trace_data.txt Done. This lets the developer easily see the average power and the variability of power, which is helpful for getting a sense of how consistent the results are and therefore (in steady-state scenarios) how meaningful they are. This format has been tested for a few weeks on a Battor equipped SurfaceBook. Bug: 751863 Change-Id: I57af162f183a4d65388c88c901573cd6720ae2b8 Reviewed-on: https://chromium-review.googlesource.com/609385 Reviewed-by: Primiano Tucci <primiano@chromium.org> Reviewed-by: Charlie Andrews <charliea@chromium.org> Commit-Queue: Bruce Dawson <brucedawson@chromium.org> Cr-Commit-Position: refs/heads/master@{#500344}
- Loading branch information
1 parent
b6b472f
commit 6cca2c0
Showing
8 changed files
with
157 additions
and
27 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters