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

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


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

chromium-rel-win7-gpu-intel

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

=== 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: winx64intel_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/Naver
  Change       : 5.09% | 2390.73766666 -> 2280.16866667

Revision             Result                  N
chromium@474979      2390.74 +- 109.156      9       good
chromium@475016      2403.26 +- 139.723      14      good
chromium@475025      2400.97 +- 139.47       9       good
chromium@475028      2387.46 +- 116.348      9       good
chromium@475029      2386.92 +- 112.603      6       good
chromium@475030      2280.08 +- 12.6263      6       bad       <--
chromium@475034      2278.08 +- 18.9233      6       bad
chromium@475052      2306.76 +- 243.068      9       bad
chromium@475125      2280.17 +- 19.6951      6       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=Naver loading.desktop

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

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


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