Issue metadata
Sign in to add a comment
|
1.6% regression in system_health.memory_mobile at 487901:488028 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973189266582172784
,
Jul 24 2017
,
Jul 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Matthew Halpern Commit : cd7e31fb911a98c7dc021d543e9dea8c553cdb1f Date : Wed Jul 19 20:50:43 2017 Subject: Enable GRC Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_tools/load_tools_dropbox Change : 0.27% | 13856064.0 -> 13893473.3333 Revision Result N chromium@487900 13856064 +- 38682.9 6 good chromium@487964 13846783 +- 28964.5 6 good chromium@487966 13844291 +- 19131.2 6 good chromium@487967 13851974 +- 22574.0 6 good chromium@487968 13894195 +- 13311.8 6 bad <-- chromium@487972 13891575 +- 18442.6 6 bad chromium@487980 13891317 +- 31465.1 6 bad chromium@487996 13895505 +- 20200.7 6 bad chromium@488028 13893473 +- 11806.7 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=load.tools.dropbox 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/8973189266582172784 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 24 2017