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

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


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

chromium-rel-win7-dual

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

=== 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_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/Naver
  Change       : 7.09% | 2438.89611111 -> 2270.68449999

Revision             Result                  N
chromium@474985      2438.9 +- 130.973       9      good
chromium@475011      2402.08 +- 147.017      9      good
chromium@475024      2393.54 +- 130.656      6      good
chromium@475027      2403.59 +- 144.927      9      good
chromium@475029      2424.52 +- 14.9934      6      good
chromium@475030      2268.63 +- 11.9437      6      bad       <--
chromium@475036      2270.88 +- 21.716       9      bad
chromium@475087      2270.68 +- 34.7968      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/8978240341954918032

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


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