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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghvPkrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghuLmqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghv3fvgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-pHq-QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghtezrgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghuDVqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghpq7oQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghpLUvAoM


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

chromium-rel-mac11
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-intel
chromium-rel-win7-x64-dual
linux-release

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

===== 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@408160  54.0726  2.41192   8  good
chromium@408169  54.095   0.339236  8  good
chromium@408171  54.3778  2.14425   8  good
chromium@408172  58.5531  0.29216   8  bad    <--
chromium@408173  58.3818  0.534636  8  bad
chromium@408177  57.8801  1.08467   8  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 632640

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_filters_cases
Test Metric: frame_times/http___rawgit.com_WebKit_webkit_master_PerformanceTests_Animometer_developer.html?test-interval_20_display_minimal_controller_fixed_frame-rate_50_kalman-process-error_1_kalman-measurement-error_4_time-measurement_performance_suite-name_Animometer_test-name_Focus_complexity_100
Relative Change: 6.34%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6609
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812964452875296


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

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