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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghqK-pgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghpmXqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICght7qpwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-rfRpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-pPc5QoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghqXbswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxqLaqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghr-vqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgutLQ4AoM


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

chromium-rel-mac10
chromium-rel-mac11
chromium-rel-win7-dual
chromium-rel-win7-x64-dual

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

===== 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@408170  68.0412  2.54321  5  good
chromium@408171  66.9876  2.14869  5  good
chromium@408172  60.764   1.87815  5  bad    <--
chromium@408173  61.0951  1.31701  5  bad
chromium@408176  61.7243  2.33068  5  bad
chromium@408182  60.1442  2.27111  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 632642

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.top_25_smooth
Test Metric: percentage_smooth/Blogger
Relative Change: 11.61%
Score: 99.8

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_11_perf_bisect/builds/774
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005812820283368384


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

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