New issue
Advanced search Search tips

Issue 893868 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 893862
Owner:
Closed: Oct 10
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

5.4%-36.1% regression in media.mobile at 597295:597387

Project Member Reported by wolenetz@chromium.org, Oct 9

Issue description

These 16 alerts look valid, though more recently their traces have *more* than recovered (better than before these alerts).

Doing a bisect to help inform regression culprit owner of this (though the regression itself might already have been fixed).

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

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


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

Android Nexus5 Perf
android-nexus5x-perf

media.mobile - Benchmark documentation link:
  None
Cc: eirage@chromium.org
Owner: eirage@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/12c90728e40000

Revert "solid color quads workaround for use-zoom-for-dsf" by eirage@chromium.org
https://chromium.googlesource.com/chromium/src/+/d7d5990bc6b25d7b7ce711b035147030e778879a
cpu_time_percentage: 0.434 → 0.5846 (+0.1506)

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

Benchmark documentation link:
  None
Mergedinto: 893862
Status: Duplicate (was: Assigned)

Sign in to add a comment