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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwtfetQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwo2-_QgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwo2-vQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwq-fswkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgoqn3tAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwoWCsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgotTfqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgorycoQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwo-R8ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgov6PtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgovzSvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwqTZ9ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgooKstgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgov7TpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwsb4tQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgwr7bvgkM


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

chromium-rel-mac11

===== 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[1] for all[2] platforms.
This 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.

[1] In this case, "begin frame scheduling" means browser->renderer
begin frame ticks instead of sending vsync information and having
a synthetic source on the renderer side.

[2] MUS is not hooked up to begin frame scheduling yet, but
mojo:mash_session in an "oxygen" build still works with this patch
applied.  Blimp also doesn't use begin frame scheduling and will
eventually just be transitioned to a synthetic begin frame source
for its engine half.

CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Review-Url: https://codereview.chromium.org/1939253002
Cr-Commit-Position: refs/heads/master@{#401796}
Commit  : f2d7f5e1891703ec4384ededd80f896816921204
Date    : Fri Jun 24 02:43:08 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev      N  Good?
chromium@401787  16.6842  0.00197162   5  good
chromium@401795  16.6809  0.00204573   5  good
chromium@401796  16.6665  0.00625048   5  bad    <--
chromium@401797  16.6667  0.00189863   5  bad
chromium@401799  16.6664  0.000974375  5  bad
chromium@401802  16.6684  0.00380661   5  bad
chromium@401816  16.6642  0.00255395   5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 623608

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests smoothness.tough_webgl_cases
Test Metric: frame_times/http___www.khronos.org_registry_webgl_sdk_demos_google_particles_index.html
Relative Change: 0.12%
Score: 99.9

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


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

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