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

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


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

android-nexus5
android-nexus5X

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14907a1b240000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14907a1b240000

Roll src/third_party/catapult f989b62823cb..484f9f764dc5 (1 commits) by catapult-chromium-autoroll@skia-buildbots.google.com.iam.gserviceaccount.com
https://chromium.googlesource.com/chromium/src/+/80863fcdfdb7ce776922a92a5e04c990ea814913
2259 → 1.82e+04 (+1.594e+04)

Assigning to sheriff sullivan@chromium.org because "Roll src/third_party/catapult f989b62823cb..484f9f764dc5 (1 commits)" is a roll.

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

The CL in question is:
git log f989b62823cb..484f9f764dc5 --date=short --no-merges --format='%ad %ae %s'
2018-06-27 sarath.singapati@huawei.com Corrected the traffic settings to reflect the settings by devtool.

The traffic settings were too fast before, so now that they're slower the page loads are expected to get slower.