Issue metadata
Sign in to add a comment
|
8% regression in system_health.memory_mobile at 501054:501177 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 13 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8968540951257295568
,
Sep 13 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/browse_social/browse_social_pinterest_infinite_scroll Revision Result N chromium@501053 136720433 +- 38936095 15 good chromium@501177 138265003 +- 22002675 11 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.social.pinterest.infinite.scroll 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/8968540951257295568 For feedback, file a bug with component Speed>Bisection
,
Oct 24 2017
Not sure what happened here, but these all look like a return to normal levels. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 13 2017