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

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


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

android-nexus6
android-one

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

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

Hi ksakamoto@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 : Kunihiko Sakamoto
  Commit : 40fe85bc5961c4201e515fc67cbf4c487bd5aecd
  Date   : Tue Aug 08 03:35:28 2017
  Subject: Convert loading.mobile page set to WprGo

Bisect Details
  Configuration: android_nexus6_perf_bisect
  Benchmark    : loading.mobile
  Metric       : timeToFirstMeaningfulPaint_avg/Regular-3G/FlipKart
  Change       : 250.23% | 3732.961 -> 13073.766

Revision             Result                  N
chromium@492500      3732.96 +- 1142.61      6      good
chromium@492513      3590.56 +- 387.555      6      good
chromium@492520      4122.0 +- 1957.98       6      good
chromium@492521      12817.5 +- 2678.95      6      bad       <--
chromium@492522      11630.0 +- 446.22       6      bad
chromium@492523      11758.9 +- 768.37       6      bad
chromium@492526      11547.1 +- 592.062      6      bad
chromium@492552      13073.8 +- 3541.49      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/8971643899499934944


For feedback, file a bug with component Speed>Bisection

These are expected performance characteristics change by WPRGo switch.
See  bug 756481  for some detailed analysis for loading.desktop benchmark case.