Issue metadata
Sign in to add a comment
|
3.9%-7.8% regression in system_health.memory_mobile at 1530664957:1530683939 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 10
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8941357404851464224
,
Jul 12
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: c25ef3fad93831154e1e11a48a39c33640a49669 bad_revision : 586e669185bb8753b539c20d8a039a7983df7608 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: webview-phone-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_social/browse_social_tumblr_infinite_scroll Change : 7.42% | 127217325.333 -> 136660994.667 Revision Result N android-chrome@4152f619ce 127217325 +- 1188302 6 good android-chrome@c25ef3fad9 128242520 +- 2247407 6 good android-chrome@586e669185 136660995 +- 1135746 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-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.tumblr.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/8941357404851464224 For feedback, file a bug with component Speed>Bisection
,
Aug 2
,
Aug 2
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 10