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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmauQsQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmdHCoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2fSVpgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2aL-uAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgmbuAugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg2YbhvwkM


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

chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11

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

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

Hi skyostil@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 : scheduler: Don't throttle 0x0 frames
Author  : skyostil
Commit description:
  
This patch avoids throttling requestAnimationFrame and timers inside 0x0
frames. The reason is that some websites (e.g., GMail) use cross origin
0x0 frames to drive UI logic and throttling these frames causes
breakage. This change also makes us match Safari's behavior.

This patch also removes the test for throttling out-of-process iframes,
because it turns out the viewport intersection code is not able to
compute intersections across process boundaries. This capability will be
restored when IntersectionObserver gains support for out-of-process
iframes.

BUG= 644217 

Review-Url: https://codereview.chromium.org/2333653002
Cr-Commit-Position: refs/heads/master@{#418174}
Commit  : b83d755a52a7fe9792af9ee360e551c157ad576e
Date    : Tue Sep 13 05:18:45 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@418157  1068.67  9.02589  6  good
chromium@418169  1062.4   13.4276  5  good
chromium@418172  1066.4   9.76217  5  good
chromium@418173  1069.0   6.733    4  good
chromium@418174  1366.0   16.9558  5  bad    <--
chromium@418175  1357.2   9.52365  5  bad
chromium@418180  1338.8   51.5335  5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 647009

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

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


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

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

Looks like this is mainly Google Plus and also Google Docs to a lesser extent. Unfortunately we can't throttle 0x0 frames without breaking things so we'll need to live this this regression.