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

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


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

chromium-rel-mac11

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

=== Auto-CCing suspected CL author erikchen@chromium.org ===

Hi erikchen@chromium.org, the bisect results pointed to your CL below as possibly
causing a regression. Please have a look at this info and see whether
your CL be related.


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


===== SUSPECTED CL(s) =====
Subject : Revert of Enable RenderPassDrawQuad promotion to CALayer. (patchset #1 id:1 of https://codereview.chromium.org/2183333002/ )
Author  : erikchen
Commit description:
  
Reason for revert:
Has correctness problems:
https://bugs.chromium.org/p/chromium/issues/detail?id=632613#c5

And likely performance problems:
https://bugs.chromium.org/p/chromium/issues/detail?id=632636

Original issue's description:
> Enable RenderPassDrawQuad promotion to CALayer.
>
> This CL enables the Core Animation compositor's implementation of CSS filter
> effects.
>
> BUG= 581526 
> CQ_INCLUDE_TRYBOTS=master.tryserver.blink:linux_precise_blink_rel
>
> Committed: https://crrev.com/c2e44129f9712162be14a1a054225e29d89b1296
> Cr-Commit-Position: refs/heads/master@{#408216}

TBR=ccameron@chromium.org,tandrii@google.com
# Not skipping CQ checks because original CL landed more than 1 days ago.
BUG= 581526 

Review-Url: https://codereview.chromium.org/2193623004
Cr-Commit-Position: refs/heads/master@{#408693}
Commit  : bfdc4df9d2396016f8fa0b7d2070a998f343ca3e
Date    : Fri Jul 29 18:26:23 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@408662  4479.8  56.4774  5  good
chromium@408679  4471.8  53.1573  5  good
chromium@408687  4441.2  13.6455  5  good
chromium@408691  4477.6  62.3362  5  good
chromium@408692  4449.8  71.2931  5  good
chromium@408693  4838.2  33.4993  5  bad    <--
chromium@408695  4755.0  103.053  5  bad

Bisect job ran on: mac_10_11_perf_bisect
Bug ID: 633107

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

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


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

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

This regression is expected, as I've reverted the CL that switches Chrome to a lower power path.