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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgssu_5woM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8t3zuAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8sqUqwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8r3WvAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgst_sqwkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8urZqgoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiozbrQoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8qrrtQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8u7KsAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgsr-ntQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgivLatAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgiqrmswoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8rXFpAoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgipia5AoM


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

chromium-rel-win10
chromium-rel-win7-gpu-ati
chromium-rel-win7-gpu-intel
chromium-rel-win7-gpu-nvidia
chromium-rel-win7-x64-dual
chromium-rel-win8-dual
win-zenbook

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

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

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

Hi kouhei@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 : HTMLDocumentParser: Dedupe member inits by moving them into in-class init
Author  : kouhei
Commit description:
  
BUG=None

Review-Url: https://codereview.chromium.org/2041013004
Cr-Commit-Position: refs/heads/master@{#403876}
Commit  : 630d84f64ee2f1d54d2627828f1ee593e85e2327
Date    : Wed Jul 06 09:47:25 2016


===== TESTED REVISIONS =====
Revision         Mean     Std Dev      N  Good?
chromium@403866  993876   2.17793e-10  5  good
chromium@403874  993876   1.93053e-10  5  good
chromium@403875  993876   1.74623e-10  5  good
chromium@403876  1002068  1.00819e-10  5  bad    <--
chromium@403878  1002068  1.16415e-10  5  bad
chromium@403882  1002068  1.16415e-10  5  bad

Bisect job ran on: win_x64_perf_bisect
Bug ID: 628281

Test Command: src/tools/perf/run_benchmark -v --browser=release_x64 --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop
Test Metric: load_games-memory:chrome:all_processes:reported_by_chrome:partition_alloc:effective_size_avg/load_games_lazors
Relative Change: 0.82%
Score: 99.9

Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/win_x64_perf_bisect/builds/1401
Job details: https://chromeperf.appspot.com/buildbucket_job_status/9004252220103365648


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

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

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.