Issue metadata
Sign in to add a comment
|
1.6% regression in memory.top_10_mobile at 509708:509759 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964939017744457184
,
Oct 23 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:webview:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/http_www_baidu_com_s_word_google Revision Result N chromium@509707 36175427 +- 489954 21 good chromium@509759 36219153 +- 641038 21 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=http.www.baidu.com.s.word.google memory.top_10_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964939017744457184 For feedback, file a bug with component Speed>Bisection
,
Jan 8 2018
small regression; bisect can't repro. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 23 2017