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

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


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

android-nexus7v2

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

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

Hi machenbach@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 : Michael Achenbach
  Commit : e93cb0e2b895f5813affb1df033d36a03ab222f6
  Date   : Wed Nov 22 09:42:03 2017
  Subject: Revert "[heap] Removed keep-one-unused-page concept in sweeper."

Bisect Details
  Configuration: android_nexus7_perf_bisect
  Benchmark    : memory.top_10_mobile
  Metric       : memory:chrome:all_processes:reported_by_os:system_memory:private_dirty_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus
  Change       : 5.60% | 50672230.0 -> 53509392.6667

Revision                           Result                   N
chromium@518611                    50672230 +- 1861474      6      good
chromium@518620                    51011960 +- 1304320      6      good
chromium@518624                    50763707 +- 2049769      6      good
chromium@518626                    50603727 +- 556054       6      good
chromium@518626,v8@25a753383e      50854027 +- 1056022      6      good
chromium@518626,v8@e93cb0e2b8      53737165 +- 551093       6      bad       <--
chromium@518626,v8@ffa30ced17      53622477 +- 775822       6      bad
chromium@518627                    54205712 +- 954070       6      bad
chromium@518628                    53302099 +- 729535       6      bad
chromium@518644                    53530555 +- 948658       6      bad
chromium@518677                    53509393 +- 557321       6      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=android-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=http.www.amazon.com.gp.aw.s.k.nexus memory.top_10_mobile

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

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


For feedback, file a bug with component Speed>Bisection

This was a revert. Assigning to original author.

Issue 788360 has been merged into this issue.

Issue 788353 has been merged into this issue.

Issue 788355 has been merged into this issue.

 Issue 788362  has been merged into this issue.

Issue 788413 has been merged into this issue.

 Issue 788366  has been merged into this issue.