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

Issue 886669 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 886668
Owner:
Closed: Sep 24
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug-Regression



Sign in to add a comment

23.8%-37.4% regression in loading.mobile at 591671:591738

Project Member Reported by alexclarke@chromium.org, Sep 19

Issue description

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

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


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

Android Nexus5 Perf

loading.mobile - Benchmark documentation link:
  https://bit.ly/loading-benchmarks
Cc: leszeks@chromium.org
Owner: leszeks@chromium.org
Status: Assigned (was: Untriaged)
📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/146da23f640000

[config] Enable scheduled script streaming field trial by leszeks@chromium.org
https://chromium.googlesource.com/chromium/src/+/7eb2bb6769b38736fc75a12c15563c4a69f1a61f
431.6 → 588.2 (+156.6)

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

Benchmark documentation link:
  https://bit.ly/loading-benchmarks
Mergedinto: 885053
Status: Duplicate (was: Assigned)
Mergedinto: -885053 886668

Sign in to add a comment