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

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


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

linux-release

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

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

Hi kinuko@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 : Pass per-frame task runners to Workers (when possible)
Author  : kinuko
Commit description:
  
- For in-process workers (i.e. dedicated/compositor workers): always use
  the associated document's task runners
- For out-of-process workers (i.e. service/shared workers): keep using the
  default task runner of the main thread, but via TaskRunnerHelper so
  we could still start using different task runners for different tasks
  (e.g. loading vs timer) if we want.

BUG= 627034 

Review-Url: https://codereview.chromium.org/2163983004
Cr-Commit-Position: refs/heads/master@{#408652}
Commit  : 66b07a326160fed57046fbb454f424a302d4cc6b
Date    : Fri Jul 29 16:30:00 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@408636  59132250  335665   5  good
chromium@408646  58785963  321270   5  good
chromium@408651  59084510  300971   5  good
chromium@408652  60669514  238000   5  bad    <--
chromium@408653  60556494  347346   5  bad
chromium@408655  60582376  439350   5  bad
chromium@408674  60500745  213799   5  bad

Bisect job ran on: linux_perf_bisect
Bug ID: 633176

Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: browse_social-memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_social_twitter
Relative Change: 2.31%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/linux_perf_bisect/builds/6614
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005530132040076672


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

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

Perf sheriff ping: reminder to follow up on possible performance issues

Temporarily declaring bankruptcy on the *desktop* system health benchmark.
The number of alerts became unmanageable and the overall process needs to be improved to make it sustainable.
The alerts have been turned off and I'm archiving the outstanding regressions.
Note: this is just about desktop, the mobile system health stays up.