Issue metadata
Sign in to add a comment
|
4.6% regression in system_health.memory_mobile at 488929:489051 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972808770072587632
,
Jul 28 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : mastiz Commit : c63d78c7a25a50f2fdfa0ab5cbb5566a21a6774e Date : Mon Jul 24 09:23:04 2017 Subject: Always prefer 192x192 on mobile, also for touch icons Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/browse_news/browse_news_washingtonpost Change : 3.87% | 26700288.0 -> 27732992.0 Revision Result N chromium@488928 26700288 +- 387559 6 good chromium@488932 26573141 +- 313627 6 good chromium@488934 26688512 +- 270460 6 good chromium@488935 27576661 +- 262363 6 bad <-- chromium@488936 27707733 +- 349503 6 bad chromium@488944 27771904 +- 236347 6 bad chromium@488959 27846315 +- 167152 6 bad chromium@488990 27667456 +- 352542 6 bad chromium@489051 27732992 +- 297574 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=browse.news.washingtonpost 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/8972808770072587632 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 28 2017