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

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


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

chromium-rel-win7-gpu-ati

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

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

Suspected Commit
  Author : jochen
  Commit : b4c4f2c525c4bc3e1494291cb8b83ebbb298c050
  Date   : Mon Apr 10 14:48:41 2017
  Subject: Explicitly tell the preload request where to take the referrer from

Bisect Details
  Configuration: winx64ati_perf_bisect
  Benchmark    : page_cycler_v2.intl_ja_zh
  Metric       : timeToFirstMeaningfulPaint_avg/pcv1-warm/http___ruten.com.tw_
  Change       : 94.56% | 349.678500003 -> 616.661071426

Revision             Result                  N
chromium@463237      349.679 +- 9.17999      14      good
chromium@463258      348.72 +- 2.9926        14      good
chromium@463261      349.219 +- 5.44549      14      good
chromium@463263      349.336 +- 5.88042      21      good
chromium@463264      539.696 +- 532.295      14      bad       <--
chromium@463269      532.341 +- 660.514      21      bad
chromium@463279      582.416 +- 457.173      14      bad
chromium@463322      616.661 +- 452.811      14      bad

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

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

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


| 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!