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

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


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

health-plan-clankium-phone

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

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

Hi yiyix@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 : yiyix
  Commit : be2578711ee47f8b8a5ba8b15108dedb50a27367
  Date   : Tue May 22 16:47:54 2018
  Subject: Fix regression in thread_times.key_mobile_sites_smooth

Bisect Details
  Configuration: clankium-phone-perf-bisect
  Benchmark    : system_health.memory_mobile
  Metric       : memory:chrome:all_processes:reported_by_chrome:java_heap:allocated_objects_size_avg/load_news/load_news_irctc
  Change       : 8.56% | 69493081.3333 -> 63543964.0

Revision                                       Result                   N
android-chrome@f43509882b                      69493081 +- 519015       6      good
android-chrome@b50c37440c                      69482720 +- 149570       6      good
android-chrome@b50c37440c,chromium@560639      69442848 +- 122598       6      good
android-chrome@b50c37440c,chromium@560648      69459116 +- 133421       6      good
android-chrome@b50c37440c,chromium@560652      69371961 +- 194940       6      good
android-chrome@b50c37440c,chromium@560653      63509259 +- 78538.2      6      bad       <--
android-chrome@b50c37440c,chromium@560654      63519000 +- 77322.3      6      bad
android-chrome@b50c37440c,chromium@560656      63508387 +- 20396.5      6      bad
android-chrome@b50c37440c,chromium@560690      63514141 +- 36725.9      6      bad
android-chrome@3e4ba1f0ce                      63495839 +- 52659.0      6      bad
android-chrome@5c07f907f2                      63543964 +- 64028.8      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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.irctc system_health.memory_mobile

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

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


For feedback, file a bug with component Speed>Bisection

the improvement was due to this cl, https://chromium-review.googlesource.com/c/chromium/src/+/1029733 and it has cause more 20 regression in other metrics. the cl mentioned here, has fixed those regressions and  smoothness.top_25_smooth timing is back to the point before the fake improvement. No bug.