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

Issue 903151 link

Starred by 1 user
Status: Duplicate
Merged: issue 905162
Owner:
oysteine@google.com
Closed: Nov 27
Cc:
oysteine@google.com
█ alexclarke@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

8.5%-9.7% regression in power.desktop at 604449:604493

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=903151

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


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

mac-10_13_laptop_high_end-perf

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

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

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

Perfetto: Fix for worker threads not finalizing proto packets by oysteine@google.com
https://chromium.googlesource.com/chromium/src/+/d420ce980291dbdee3d8a68594afbbfe5b75fbb4
cpu_time_percentage: 0.1655 → 0.1723 (+0.006863)

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

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

Comment 4 by oysteine@google.com, Nov 27

Mergedinto: 905162
Status: Duplicate (was: Assigned)
►

Sign in to add a comment