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

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


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

chromium-rel-mac10

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

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. 

===== BISECT JOB RESULTS =====
Status: failed


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@418233  20185968  41580.0  5  good
chromium@418373  22460553  191612   5  bad

Bisect job ran on: mac_10_10_perf_bisect
Bug ID: 647645

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:old_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:old_space:effective_size_avg
Relative Change: 10.74%
Score: 0

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


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

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

=== BISECT JOB RESULTS ===
Perf regression found but unable to narrow commit range

Build failures prevented the bisect from narrowing the range further.


Bisect Details
  Configuration: mac_10_10_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:old_space:effective_size_avg/memory:chrome:renderer_processes:reported_by_chrome:v8:heap:old_space:effective_size_avg

Suspected Commit Range
  1 commits in range
  https://chromium.googlesource.com/chromium/src/+log/88f013bd979ec30333bd7ce6c0bd2e0b5f6f2742..dfd9a7c5ba710ee862117267ac6c9ba343bc94f7


Revision             Result                   N
chromium@418233      20185968 +- 41580.0      5      good
chromium@418373      22460553 +- 191612       5      bad

Please refer to the following doc on diagnosing memory regressions:
  https://chromium.googlesource.com/chromium/src/+/master/docs/memory-infra/memory_benchmarks.md

To Run This Test
  src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop

Debug Info
  https://chromeperf.appspot.com/buildbucket_job_status/8982619879188560784

Is this bisect wrong?
  https://chromeperf.appspot.com/bad_bisect?try_job_id=5333612713476096


| 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 Speed>Bisection.  Thank you!