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

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


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

chromium-rel-win8-dual

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

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

Suspected Commit
  Author : samans
  Commit : f26257b9ee4b7e722cc05468ceecbcf3f920be22
  Date   : Fri May 26 16:37:45 2017
  Subject: Send BeginFrames for the renderer using Mojo

Bisect Details
  Configuration: win_8_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/Naver
  Change       : 10.09% | 2510.12644444 -> 2292.47933334

Revision             Result                  N
chromium@474975      2510.13 +- 359.108      9      good
chromium@475005      2478.1 +- 209.891       9      good
chromium@475020      2473.35 +- 188.662      6      good
chromium@475028      2467.01 +- 188.935      6      good
chromium@475029      2502.41 +- 14.79        6      good
chromium@475030      2268.73 +- 176.622      9      bad       <--
chromium@475032      2287.36 +- 8.95535      6      bad
chromium@475035      2291.43 +- 13.5811      9      bad
chromium@475095      2292.48 +- 12.8802      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=Naver loading.desktop

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

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


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