New issue
Advanced search Search tips

Issue 879735 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 4
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

A zero-to-nonzero to 1% regression in rendering.mobile at 587336:587436

Project Member Reported by mustaq@chromium.org, Aug 31

Issue description

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

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


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: 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/11bcbf33640000

turn off use-zoom-for-dsf on Android by eirage@chromium.org
https://chromium.googlesource.com/chromium/src/+/14d5c4330c08ac9bcdcda7960561e3e92c135da6
0 → 0.21 (+0.21)

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions
Status: WontFix (was: Assigned)
Caused by turning off --use-zoom-for-dsf (it was turned on on Jul 31)

Sign in to add a comment