Issue metadata
Sign in to add a comment
|
4.4%-4.8% regression in system_health.memory_mobile at 1527090871:1527108777 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 25 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8945556579781825568
,
May 25 2018
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: go-webview-phone-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/load_search/load_search_yandex Change : 4.92% | 3817543.42857 -> 4005409.71429 Suspected Commit Range 3 commits in range Unknown depot, please contact team to have this added. Revision Result N android-chrome@d7788bd380 3817543 +- 72577.2 14 good android-chrome@a3eda486ee --- --- build failure android-chrome@791e44c6d4 --- --- build failure android-chrome@e7e9bdf521 3984243 +- 100967 14 bad android-chrome@40513d8129 4005410 +- 67928.2 14 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=load.search.yandex 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/8945556579781825568 For feedback, file a bug with component Speed>Bisection
,
Jul 4
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, May 25 2018