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

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


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

chromium-rel-mac10

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

===== BISECT JOB RESULTS =====
Status: completed


=== Bisection aborted ===
The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression.
Please contact the the team (see below) if you believe this is in error.

=== Warnings ===
The following warnings were raised by the bisect job:

 * Bisect failed to reproduce the regression with enough confidence.

===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N   Good?
chromium@408243  1570.17  27.0011  12  good
chromium@408277  1581.63  19.2572  8   bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 632707

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.gpu_rasterization.top_25
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: 1.57%
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2240
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005800190913594112


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

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

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

Trying another bisect.

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

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@408700  1632.4  39.5765  5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 632707

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.gpu_rasterization.top_25
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: None
Score: 0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2249
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005540981857310512


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

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

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

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

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

Started a few bisects, some on individual pages that regressed.

===== 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@408100  2275.0  25.0998  5  good
chromium@408138  2166.2  321.352  5  good
chromium@408157  2311.4  13.2966  5  good
chromium@408166  2294.2  15.3199  5  good
chromium@408171  2299.6  21.2203  5  good
chromium@408172  3008.0  31.3608  5  bad    <--
chromium@408173  3013.8  37.023   5  bad
chromium@408175  3015.6  29.3479  5  bad
chromium@408250  2972.6  33.7387  5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 632707

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.gpu_rasterization.top_25
Test Metric: idle_wakeups_total/http___games.yahoo.com
Relative Change: 30.66%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2252
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005518368994757008


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

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

===== 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@408100  1716.2   23.4989  5  good
chromium@408138  1596.4   287.644  5  good
chromium@408157  1735.6   24.3988  5  good
chromium@408166  1741.2   10.5688  5  good
chromium@408171  1736.25  20.4503  8  good
chromium@408172  1781.38  243.347  8  bad    <--
chromium@408173  1866.13  22.5796  8  bad
chromium@408175  1860.4   18.0083  5  bad
chromium@408250  1852.2   22.698   5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 632707

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.gpu_rasterization.top_25
Test Metric: idle_wakeups_total/http___www.ebay.com
Relative Change: 7.92%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2253
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005518345534082384


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

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

===== 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@408100  1539.58  47.3084  12  good
chromium@408150  1562.6   22.3226  5   good
chromium@408163  1558.0   19.4036  5   good
chromium@408169  1556.8   39.2518  5   good
chromium@408171  1586.0   12.2678  5   good
chromium@408172  1629.2   19.1494  5   bad    <--
chromium@408175  1661.8   6.83374  5   bad
chromium@408200  1629.0   49.8689  12  bad
chromium@408300  1644.13  45.4138  8   bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 632707

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests power.gpu_rasterization.top_25
Test Metric: idle_wakeups_total/idle_wakeups_total
Relative Change: 4.69%
Score: 98.0

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2251
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005518467095251872


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

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