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

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


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

chromium-rel-mac-retina

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

===== BISECT JOB RESULTS =====
Status: completed


===== SUSPECTED CL(s) =====
Subject : Turn on enable begin frame scheduling by default
Author  : enne
Commit description:
  
This turns on --enable-begin-frame-scheduling for all platforms but mus
and Blimp.  This change means browser->renderer begin frame ticks
instead of sending vsync information and having a synthetic source on
the renderer side.  This feature was already on for Android so should
only be a real change for desktop / ChromeOS platforms.

Lots of cleanup can follow from this like removing all commit vsync /
authoritative vsync / CompositorVSyncManager things, but this is a
smaller patch to suss out any performance regressions.

This previously landed and regressed a number of metrics.  Some of these
have been investigated and fixed and the rest are WontFix.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review-Url: https://codereview.chromium.org/1939253002
Cr-Commit-Position: refs/heads/master@{#408172}
Commit  : d020d554c9ffc0476d43f5364a47c522b64e3d9a
Date    : Wed Jul 27 17:45:34 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev      N  Good?
chromium@408154  0.102413  0.00175868   5  good
chromium@408167  0.10235   0.00192227   5  good
chromium@408171  0.102414  0.00177947   5  good
chromium@408172  0.112429  0.00176343   5  bad    <--
chromium@408173  0.113802  0.0012626    5  bad
chromium@408174  0.11506   0.00162352   5  bad
chromium@408180  0.112631  0.000742806  5  bad
chromium@408206  0.111715  0.00130847   5  bad

Bisect job ran on: mac_retina_perf_bisect
Bug ID: 632645

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests scheduler.tough_scheduling_cases
Test Metric: queueing_durations/queueing_durations
Relative Change: 9.08%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1461
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812746602159360


Not what you expected? We'll investigate and get back to you!
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5860568922062848

| 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 Tests>AutoBisect.  Thank you!