New issue
Advanced search Search tips

Issue 917268 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 916138
Owner:
Closed: Jan 2
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

16%-41.6% regression in performance_browser_tests at 617807:617839

Project Member Reported by kouhei@google.com, Dec 21

Issue description

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

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


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

mac-10_12_laptop_low_end-perf
mac-10_13_laptop_high_end-perf
Cc: kylec...@chromium.org
Owner: kylec...@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/13cf0086140000

Enable OOP-D by default on mac again. by kylechar@chromium.org
https://chromium.googlesource.com/chromium/src/+/2fddbbf41249123377a3c1bcad854e35263f59d1
CastV2Performance_gpu_30fps_wifi_autothrottling: 0.7167 → 1.015 (+0.2981)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Mergedinto: 916138
Status: Duplicate (was: Assigned)

Sign in to add a comment