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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgIDgqq_1uAoM


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

chromium-rel-win8-dual

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

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

Suspected Commit
  Author : yhirano
  Commit : 91088a195969f5af61f404c9f02edc622cbe373a
  Date   : Wed May 10 05:49:31 2017
  Subject: Add Field Trial Testing Configuration for MojoLoading

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : page_cycler_v2.intl_ja_zh
  Metric       : timeToFirstContentfulPaint_avg/pcv1-warm/http___www.qq.com_
  Change       : 35.92% | 44.236 -> 28.3461666666

Revision             Result                  N
chromium@470445      44.236 +- 7.10361       6      good
chromium@470481      41.915 +- 4.31791       6      good
chromium@470486      43.4118 +- 5.37419      6      good
chromium@470488      42.587 +- 4.36609       6      good
chromium@470489      44.1665 +- 4.14752      6      good
chromium@470490      29.1262 +- 3.31749      6      bad       <--
chromium@470499      28.8552 +- 5.13067      6      bad
chromium@470516      28.3462 +- 7.83842      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http...www.qq.com. page_cycler_v2.intl_ja_zh

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8979532133396290064

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=4742915965845504


| O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq
|  X  | for more information addressing perf regression bugs. For feedback,
| / \ | file a bug with component Speed>Bisection.  Thank you!