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

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


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

chromium-rel-mac11-air

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

=== BISECT JOB RESULTS ===
Bisect was unable to run to completion

The bisect was able to narrow the range, you can try running with:
  good_revision: 137707cfcb43771e8a3d6805c3f327c22a4f87d9
  bad_revision : 2040988b1345e6ce738bd03ab7ccd5f4b73a956b

If failures persist contact the team (see below) and report the error.


Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time
  Change       : 66.84% | 259.333333333 -> 86.0

Revision             Result                  N
chromium@463670      259.333 +- 23.6502      6      good
chromium@463770      250.667 +- 5.03322      6      good
chromium@463820      251.5 +- 12.47          6      good
chromium@463833      254.167 +- 9.9415       6      good
chromium@463839      248.5 +- 8.80341        6      good
chromium@463842      251.833 +- 7.67029      6      good
chromium@463845      85.6667 +- 3.3665       6      bad
chromium@463870      86.0 +- 3.74166         6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

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

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


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

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

=== Auto-CCing suspected CL author samans@chromium.org ===

Hi samans@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


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

Suspected Commit
  Author : samans
  Commit : 2040988b1345e6ce738bd03ab7ccd5f4b73a956b
  Date   : Tue Apr 11 23:58:35 2017
  Subject: Use MojoCompositorFrameSink in RendererCompositorFrameSink

Bisect Details
  Configuration: mac_air_perf_bisect
  Benchmark    : startup.warm.blank_page
  Metric       : open_tabs_time/open_tabs_time
  Change       : 66.56% | 255.166666667 -> 85.3333333333

Revision             Result                  N
chromium@463670      255.167 +- 13.6687      6      good
chromium@463770      247.5 +- 5.24404        6      good
chromium@463820      249.333 +- 9.2376       6      good
chromium@463833      247.833 +- 16.5781      6      good
chromium@463839      250.833 +- 6.54472      6      good
chromium@463842      249.333 +- 14.1185      6      good
chromium@463844      247.5 +- 7.44983        6      good
chromium@463845      86.0 +- 5.09902         6      bad       <--
chromium@463870      85.3333 +- 3.65148      6      bad

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --pageset-repeat=2 --also-run-disabled-tests startup.warm.blank_page

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

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


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