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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghrj-swkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghrLD4ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghsrMowkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghrPGswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghsKHogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghrLD4goM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgutHGhQgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-qqt-gkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghq79-wgM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-r_UrwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghrGzqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICght2opgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgutbLzgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghrGzqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghtqgsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-qvg6wkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg-ufTqwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgutT3tggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICghvamtAsM


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

chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual

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

===== 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@408169  19.5043  0.0674587  5  good
chromium@408171  19.5799  0.21872    5  good
chromium@408172  25.8052  0.84815    5  bad    <--
chromium@408174  26.5158  0.707447   5  bad
chromium@408178  26.0895  0.680857   5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 632638

Test Command: .\src\out\Release_x64\performance_browser_tests.exe --test-launcher-print-test-stdio=always --enable-gpu
Test Metric: TabCapturePerformance_webrtc/Capture
Relative Change: 33.76%
Score: 99.9

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


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

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