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

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


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

chromium-rel-win7-x64-dual

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

=== 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_x64_perf_bisect
  Benchmark    : loading.desktop
  Metric       : timeToFirstContentfulPaint_avg/pcv1-cold/Naver
  Change       : 6.62% | 2443.21933332 -> 2281.55666667

Revision             Result                  N
chromium@474985      2443.22 +- 32.2583      6       good
chromium@475009      2410.94 +- 127.402      6       good
chromium@475021      2409.1 +- 183.879       9       good
chromium@475027      2406.4 +- 248.066       14      good
chromium@475029      2419.64 +- 155.149      9       good
chromium@475030      2262.7 +- 144.43        9       bad       <--
chromium@475033      2286.15 +- 38.8034      9       bad
chromium@475080      2281.56 +- 14.5137      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/8978240321010122480

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


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