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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgprSFpgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvqvqQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpve1ogoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgprnUowoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpoyAtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpsKjtAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpoiSrgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpsiBrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpsjatAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpp26tAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpou4qAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpqv8oQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpqvmsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgppnq5ggM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpoy5sgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxq_brQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpov7vQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpozXugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvmmoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5uSDoAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpsyctgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpp2spQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpobCpQsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpt3drwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvmbuQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgppvctgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgppuGrwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpr2aqAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5uLApAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpsbepwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpqKGsgsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5tT4swoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpuLnuQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpoXktQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5tS2uwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvyTogsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgprTKqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5tDYoAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgprq9qgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgxq-xpQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgprrHuwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgprTjtwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpq3IrAsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpsuqqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpt7GqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpunJvQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvTNuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpt6NpgkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpvP-rwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpr6kvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5vDRoQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg5uKUtQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgpt6NpgsM


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

android-galaxy-s5
android-nexus5X
android-nexus6
android-nexus7v2
android-nexus9
android-one
chromium-rel-mac-retina
chromium-rel-mac10
chromium-rel-mac11
chromium-rel-win10
chromium-rel-win7-dual
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
linux-release

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

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

Hi hajimehoshi@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 : Refactoring: Make member variables in Resource private
Author  : hajimehoshi
Commit description:
  
This CL moves some member variables in Resource class from protected to
private to improve code health.

BUG=n/a
TEST=webkit_unit_tests

Review-Url: https://codereview.chromium.org/2199713002
Cr-Commit-Position: refs/heads/master@{#408943}
Commit  : 33e8546b6e54b2a38d9baa327f45238cf6d64c28
Date    : Mon Aug 01 11:50:46 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev  N  Good?
chromium@408942  4690145  43771.7  5  good
chromium@408943  5623748  37984.7  5  bad    <--

Bisect job ran on: android_s5_perf_bisect
Bug ID: 633527

Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile
Test Metric: load_tools-memory:chrome:all_processes:reported_by_chrome:partition_alloc:effective_size_avg/load_tools_gmail
Relative Change: 19.91%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_s5_perf_bisect/builds/873
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9005450902070891936


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

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

I wasn't able to see the graph (the URL is too long), but I guess this is the same problem as crbug/631068.

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.