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

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


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

chromium-rel-mac10
win-zenbook

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

===== 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@405481  28914550  854171   12  good
chromium@405494  29417472  774425   12  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 629106

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: load_media-memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_media_youtube
Relative Change: 0.72%
Score: 0

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


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

| 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/9006717506372001968

Wider bisect: https://build.chromium.org/p/tryserver.chromium.perf/builders/mac_10_10_perf_bisect/builds/2215

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

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

===== 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@405481  28980565  539942   12  good
chromium@405513  29504853  302698   12  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 629106

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: load_media-memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_media_youtube
Relative Change: 1.45%
Score: 0

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


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

| 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/9003876490062368128

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.