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

Issue 887074 link

Starred by 1 user
Status: Assigned
Owner:
ericrk@chromium.org
Cc:
samans@chromium.org
█ fsam...@chromium.org
ericrk@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

1.6%-125.1% regression in rendering.mobile at 587172:587302

Project Member Reported by ericrk@chromium.org, Sep 19 
Factoring out non input latency related regressions from  crbug.com/879207
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Sep 19 

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

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


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
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Sep 20

Cc: ericrk@chromium.org
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11e8aa47640000

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

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

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

Sign in to add a comment