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

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=5d1a1697914b7913dddcb80c412bb4e5eabd2cf6cb35e0a9e35a7f9aeac4f9e5


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

chromium-rel-mac-retina

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

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

Hi xunjieli@chromium.org, the bisect results pointed to your CL, please take a look at the
results.


=== BISECT JOB RESULTS ===
Perf regression found with culprit

Suspected Commit
  Author : Helen Li
  Commit : 05ee1dbfaf0aa7c03b9ea2040f0345277042d0f1
  Date   : Mon Jul 31 13:24:01 2017
  Subject: [wpr-go] Switch system_health_desktop.json to use go

Bisect Details
  Configuration: mac_retina_perf_bisect
  Benchmark    : system_health.memory_desktop
  Metric       : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_tools/load_tools_docs
  Change       : 5.73% | 75046027.4286 -> 79412059.5556

Revision             Result                   N
chromium@490743      75046027 +- 6954844      14      good
chromium@490748      75837718 +- 6074060      21      good
chromium@490750      75727867 +- 4099604      9       good
chromium@490751      77913423 +- 4169030      9       bad       <--
chromium@490752      77786787 +- 5125774      14      bad
chromium@490761      77653489 +- 5234934      14      bad
chromium@490778      79412060 +- 7320847      9       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 --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.docs system_health.memory_desktop

More information on addressing performance regressions:
  http://g.co/ChromePerformanceRegressions

Debug information about this bisect:
  https://chromeperf.appspot.com/buildbucket_job_status/8971932175995114896


For feedback, file a bug with component Speed>Bisection

The small jump is caused by switching of WebPageReplay ( Issue 730036 ).
I am applying WontFix because slight changes in performance characteristics are expected.