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

Issue 899911 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 899840
Owner:
Closed: Oct 30
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

7.8%-18.1% regression in cpu_time_percentage at 603087:603257

Project Member Reported by 42576172...@developer.gserviceaccount.com, Oct 29

Issue description

See the link to graphs below.
 
All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=899911

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


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

Win 7 Perf
mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf

power.desktop - Benchmark documentation link:
  https://bit.ly/power-benchmarks
Cc: penghuang@chromium.org
Owner: penghuang@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14b2b689e40000

Make browser UI to use OOPR as well when OOPR is enabled. by penghuang@chromium.org
https://chromium.googlesource.com/chromium/src/+/392cff8628eed1ce42f41362d2328f60768e2ce5
cpu_time_percentage: 0.09835 → 0.1165 (+0.01811)

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

Benchmark documentation link:
  https://bit.ly/power-benchmarks
Mergedinto: 899840
Status: Duplicate (was: Assigned)

Sign in to add a comment