New issue
Advanced search Search tips

Issue 880297 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 879207
Owner:
Closed: Sep 13
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.4%-100% regression in rendering.mobile at 587172:587302

Project Member Reported by maxlg@chromium.org, Sep 4

Issue description

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks
Cc: ericrk@chromium.org
Owner: ericrk@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/1024dfdb640000

Android OOP-D: Enable OOP-D for Android Waterfall by ericrk@chromium.org
https://chromium.googlesource.com/chromium/src/+/86da5de5d854b46ef4e85bbef645a1c0866ed13b
15.38 → 22.81 (+7.432)

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

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

Sign in to add a comment