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

Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?keys=agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8oqYuAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8uvrvwoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICgst_6ugoM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8raEvwsM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8uHYpAkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8u3VtQkM,agxzfmNocm9tZXBlcmZyFAsSB0Fub21hbHkYgICg8sqKugoM


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

chromium-win-clang

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

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

Hi petrcermak@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 : [system-health] Generalize loading stories to single-page stories
Author  : petrcermak
Commit description:
  
This is a preparation step for implementing interaction stories (see
https://goo.gl/Jek2NL), which are also single-page stories.

BUG=589726
CQ_EXTRA_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq

Review-Url: https://codereview.chromium.org/2092163002
Cr-Commit-Position: refs/heads/master@{#402494}
Commit  : 4a1564f3aac9977033002f4f2537ff3bc2fa62ca
Date    : Tue Jun 28 17:09:31 2016


===== TESTED REVISIONS =====
Revision         Mean      Std Dev  N  Good?
chromium@402444  10160538  574329   5  good
chromium@402477  10370253  877302   5  good
chromium@402493  10160538  574329   5  good
chromium@402494  44524339  1148657  5  bad    <--
chromium@402495  44104909  468937   5  bad
chromium@402497  43685478  574329   5  bad
chromium@402501  44104909  468937   5  bad
chromium@402510  44104909  877302   5  bad
chromium@402574  44104909  877302   5  bad
chromium@402714  43475763  1148657  5  bad

Bisect job ran on: win_perf_bisect
Bug ID: 628271

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_news-memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_news_wikipedia
Relative Change: 327.89%
Score: 99.9

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


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

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

The regression was due to re-ordering stories in the SH storyset.