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

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


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

chromium-rel-win7-gpu-ati

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

=== 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: winx64ati_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/Naver
  Change       : 5.36% | 2430.26822221 -> 2293.50433333

Revision             Result                  N
chromium@474969      2430.27 +- 41.9336      9       good
chromium@475025      2397.01 +- 167.485      9       good
chromium@475029      2397.96 +- 109.488      6       good
chromium@475030      2289.17 +- 23.7694      6       bad       <--
chromium@475031      2296.9 +- 44.8628       9       bad
chromium@475032      2299.58 +- 93.6473      14      bad
chromium@475039      2293.0 +- 28.551        14      bad
chromium@475053      2291.58 +- 16.3653      9       bad
chromium@475080      2293.5 +- 41.7667       9       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/8978240303136088832

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


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