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

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


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

chromium-rel-win7-dual

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

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. 

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

Hi rnephew@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 : Reland [Telemetry] Convert long running user stories to the System Health format.
Author  : rnephew
Commit description:
  
Requires https://codereview.chromium.org/2228103002/

BUG= 639315 

Review-Url: https://codereview.chromium.org/2320783002
Cr-Commit-Position: refs/heads/master@{#418256}
Commit  : 8a487cef9afc07dc5d9ee7392b583f1da8be274a
Date    : Tue Sep 13 15:37:50 2016


===== TESTED REVISIONS =====
Revision         Mean    Std Dev  N  Good?
chromium@418229  723102  10809.9  5  good
chromium@418254  711349  2458.04  5  good
chromium@418255  721735  11222.0  5  good
chromium@418256  806598  10471.0  5  bad    <--
chromium@418258  813579  8134.47  5  bad
chromium@418261  797388  11015.6  5  bad
chromium@418267  802760  8911.79  5  bad
chromium@418279  800235  10978.1  6  bad

Bisect job ran on: win_perf_bisect
Bug ID: 647644

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: memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:map_space:allocated_objects_size_avg
Relative Change: 10.84%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_perf_bisect/builds/6935
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9001369429599012240


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

| 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 was adding 2 test cases to system health, not a change to chrome. As lnog as the numbers have stabilized at the new values I think it would be safe to ignore this.

Marking as WontFix, feel free to reopen if you disagree with my reasoning in comment #6