New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 640054 link

Starred by 2 users
Status: Fixed
Owner:
erikc...@chromium.org
Closed: Nov 2016
Cc:
panicker@chromium.org
█ alexandermont@chromium.org
charliea@chromium.org
tdres...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug

Blocked on:
issue 640312


Sign in to add a comment

Find and implement more granular metrics that are representative of Chrome's CPU power consumption

Project Member Reported by erikc...@chromium.org, Aug 23 2016 
Design doc: https://docs.google.com/document/d/1QlX7BJDjDmHH2BuysnwYA5QqqGOW24bj6OpQzqWHFeo/edit#

We care about total power consumption, as measured by Intel MSRs or BattOr. These numbers can be noisy, since Chrome is a complex system. Intermediary metrics that provide more granularity: 
  Idle Wakeups
  CPU usage (ms per s)

Both of these can be measured by /usr/bin/powermetrics. We should implement them, and see if they are correlated with CPU power usage [I would expect so].

Comment 1 by erikc...@chromium.org, Aug 23 2016 

on macOS, the system uses another metrics "PowerMetrics" emitted by /usr/bin/powermetrics to single out processes that are "using too much power". Ideally, this metric would go down as we make performance improvements. We may also want to experiment with it to see whether it is highly correlated with Chrome's CPU power usage.

Comment 2 by nedngu...@google.com, Aug 23 2016

Cc: alexandermont@chromium.org charliea@chromium.org

Comment 3 by erikc...@chromium.org, Aug 23 2016 

nednguyen has suggested that I also take a look at the thread_times metrics based on tracing.

Comment 4 by nedngu...@google.com, Aug 23 2016

Cc: tdres...@chromium.org panicker@chromium.org

Comment 5 by erikc...@chromium.org, Aug 23 2016

Blockedon: 640312
Project Member

Comment 6 by bugdroid1@chromium.org, Aug 24 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/c40df542b75cf54fcb0382ca34f6cf191e350f6e

commit c40df542b75cf54fcb0382ca34f6cf191e350f6e
Author: catapult-deps-roller <catapult-deps-roller@chromium.org>
Date: Wed Aug 24 21:55:39 2016

Roll src/third_party/catapult/ ae022b60c..5bcf2c70f (7 commits).

https://chromium.googlesource.com/external/github.com/catapult-project/catapult.git/+log/ae022b60c580..5bcf2c70f4dd

$ git log ae022b60c..5bcf2c70f --date=short --no-merges --format='%ad %ae %s'
2016-08-24 nednguyen Show trace's url in CSV output formater.
2016-08-24 oysteine Added a demo mapper for the trace processor
2016-08-24 rmcilroy [memory-metric] Extract v8:code_and_metadata from all memory dumps
2016-08-24 erikchen Add CPU metrics for Chrome on Mac.
2016-08-24 petrcermak [merge-traces] Support multiple sub-traces in a vulcanized HTML trace
2016-08-24 benjhayden Fix single-sample Histogram sample diagnostics
2016-08-24 nednguyen [Telemetry] Add browser_test_runnner.LoadAllTestsInModule method

BUG= 640054 , 636153 

TBR=catapult-sheriff@chromium.org

Review-Url: https://codereview.chromium.org/2277473005
Cr-Commit-Position: refs/heads/master@{#414161}

[modify] https://crrev.com/c40df542b75cf54fcb0382ca34f6cf191e350f6e/DEPS
Project Member

Comment 7 by bugdroid1@chromium.org, Aug 25 2016 

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/03a86b97ad34c5d4934174b3f961d60934855e03

commit 03a86b97ad34c5d4934174b3f961d60934855e03
Author: erikchen <erikchen@chromium.org>
Date: Thu Aug 25 00:49:47 2016

mac: Add CPU measurements to power metric.

These metrics provide more granular information about the CPU usage of chrome
for performance benchmarks.

BUG= 640054 

Review-Url: https://codereview.chromium.org/2270093002
Cr-Commit-Position: refs/heads/master@{#414231}

[modify] https://crrev.com/03a86b97ad34c5d4934174b3f961d60934855e03/tools/perf/metrics/power.py

Comment 8 by erikc...@chromium.org, Nov 10 2016

Status: Fixed (was: Assigned)
►

Sign in to add a comment