New issue
Advanced search Search tips

Issue 859960 link

Starred by 1 user
Status: Duplicate
Merged: issue 860264
Owner:
enne@chromium.org
Closed: Jul 9
Cc:
enne@chromium.org
khushals...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

171.7% regression in rendering.mobile at 571636:571766

Project Member Reported by khushals...@chromium.org, Jul 3 
rendering.mobile has a bunch of regressions likely from turning on OOP raster on the perf bots. Filing a bug to track that.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Jul 3 

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

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


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

android-nexus5X
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Jul 3

Owner: enne@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/11ad9c50a40000

Turn on OOP Raster on android bots by enne@chromium.org
https://chromium.googlesource.com/chromium/src/+/d82c4fabc5cc6cbe6b475186ed9fa0216980e533
70.61 → 183.2 (+112.6)

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

Comment 4 by enne@chromium.org, Jul 9

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

Sign in to add a comment