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

Issue 903136 link

Starred by 1 user
Status: Fixed
Owner:
oysteine@chromium.org
Closed: Nov 30
Cc:
oysteine@chromium.org
█ alexclarke@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

4%-6.8% regression in power.desktop at 603929:603993

Project Member Reported by alexclarke@chromium.org, Nov 8 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Nov 8 

All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=903136

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=60272ee1ef8619ad315a96d4ff9b5f00c2841daa5014cc09ff754c21208e3208


Bot(s) for this bug's original alert(s):

Android Nexus5 Perf
linux-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

power.desktop - Benchmark documentation link:
  https://bit.ly/power-benchmarks
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Nov 8

Cc: oysteine@chromium.org
Owner: oysteine@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/16c8228be40000

Reland "Enable Perfetto by default for all telemetry tests" by oysteine@chromium.org
https://chromium.googlesource.com/chromium/src/+/3bb24369bef996b43b2d2711f0033ba472f779ea
cpu_time_percentage: 0.07642 → 0.0815 (+0.005071)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Benchmark documentation link:
  https://bit.ly/power-benchmarks

Comment 4 by oysteine@chromium.org, Nov 30

Status: Fixed (was: Assigned)
cpu_time_average is recovered after http://crrev.com/612360 (on the alerts where I can tell).
►

Sign in to add a comment