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

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


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

android-nexus5X
chromium-rel-mac-retina
chromium-rel-mac11
chromium-rel-mac11-air
chromium-rel-mac11-pro
chromium-rel-mac12
chromium-rel-mac12-mini-8gb
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
win-high-dpi

Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8962361726084372608

=== Auto-CCing suspected CL author alexilin@chromium.org ===

Hi alexilin@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Alexandr Ilin
  Commit : 698e803c4335c3e9429f580851a580b18e7daef0
  Date   : Thu Nov 16 21:07:36 2017
  Subject: Revert "Enable SpeculativePreconnect Field Trial Testing"

Bisect Details
  Configuration: android_nexus5X_perf_bisect
  Benchmark    : loading.mobile
  Metric       : cpuTimeToFirstMeaningfulPaint_avg/warm_Regular-3G/FlipKart
  Change       : 1670.34% | 77.2923333333 -> 1368.34033333

Revision             Result                  N
chromium@517139      77.2923 +- 19.1008      6      good
chromium@517182      85.7318 +- 24.7948      6      good
chromium@517188      81.9475 +- 23.263       6      good
chromium@517190      79.869 +- 17.0844       6      good
chromium@517191      1435.06 +- 94.6778      6      bad       <--
chromium@517193      1396.09 +- 131.238      6      bad
chromium@517204      1424.25 +- 128.151      6      bad
chromium@517225      1368.34 +- 114.018      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=FlipKart loading.mobile

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8962361726084372608


For feedback, file a bug with component Speed>Bisection

 Issue 787405  has been merged into this issue.

Just like I thought.

Yep, it's a field trial that was reverted due to regressions on another set of benchmarks. It's nice to see that there were some improvements as well.

Linking to the bug with original regression to save history.

 Issue 787999  has been merged into this issue.

 Issue 787999  has been merged into this issue.

 Issue 788374  has been merged into this issue.

 Issue 788673  has been merged into this issue.

 Issue 789188  has been merged into this issue.

 Issue 789696  has been merged into this issue.