New issue
Advanced search Search tips

Issue 891232 link

Starred by 1 user
Status: WontFix
Owner:
npm@chromium.org
Closed: Oct 2
Cc:
npm@chromium.org
petermarshall@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

456.8% regression in v8.browsing_mobile at 594330:594384

Project Member Reported by petermarshall@chromium.org, Oct 2 
See the link to graphs below.
Project Member

Comment 1 by 42576172...@developer.gserviceaccount.com, Oct 2 

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

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


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

Android Nexus6 WebView Perf

v8.browsing_mobile - Benchmark documentation link:
  None
Project Member

Comment 3 by 42576172...@developer.gserviceaccount.com, Oct 2

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

Paint timing: revert back to swap-time by npm@chromium.org
https://chromium.googlesource.com/chromium/src/+/f962a47e219a605eb9648251df3d76471fe06bd9
5.186 → 28.34 (+23.16)

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

Benchmark documentation link:
  None

Comment 4 by npm@chromium.org, Oct 2

Status: WontFix (was: Assigned)
It looks like this regression corresponds to a recent dip, so WontFixing this. The graph is noisy which would explain why the bisect is pointing to an incorrect culprit.
►

Sign in to add a comment