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

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


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

chromium-rel-win7-x64-dual

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

===== 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@408136  36.89    0.386642  5  good
chromium@408168  36.3544  0.352377  5  good
chromium@408170  36.9316  0.403271  5  good
chromium@408171  36.2824  1.14929   5  good
chromium@408172  40.3148  0.730931  5  bad    <--
chromium@408177  40.1877  0.344363  5  bad
chromium@408184  40.0492  0.909201  5  bad
chromium@408200  40.79    0.614348  5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 632648

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.gpu_rasterization.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: 10.57%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1360
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812666473491168


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

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