Issue metadata
Sign in to add a comment
|
3.6%-11.6% regression in system_health.memory_mobile at 1531808220:1531887020 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 23
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8940223171021241984
,
Jul 23
=== BISECT JOB RESULTS === NO Perf regression found 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/background_search/background_search_google Change : 2.67% | 7254968.19048 -> 7448546.85714 Revision Result N android-chrome@0c10befa36 7254968 +- 715475 21 good android-chrome@21eb56d664 7448547 +- 513708 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=background.search.google 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/8940223171021241984 For feedback, file a bug with component Speed>Bisection
,
Jul 23
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8940210600521798336
,
Jul 23
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Frank Tang Commit : 02fe0c2477e1589a9d0df688f6f1be1322d0d306 Date : Mon Jul 16 18:37:25 2018 Subject: [Intl] Plumb through locale and options from Array#toLocaleString Bisect Details Configuration: webview-low-end-phone-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/background_search/background_search_google Change : 6.98% | 6706820.28571 -> 7191136.28571 Revision Result N android-chrome@3be694fa46 6706820 +- 90992.9 14 good android-chrome@79cd82244a 6829190 +- 270015 21 good android-chrome@79cd82244a,chromium@575459 6744035 +- 263147 9 good android-chrome@79cd82244a,chromium@575465 6765843 +- 262500 9 good android-chrome@79cd82244a,chromium@575466 6653491 +- 104985 6 good android-chrome@79cd82244a,chromium@575466,v8@02fe0c2477 7205147 +- 101079 6 bad <-- android-chrome@79cd82244a,chromium@575466,v8@66a2db59c1 7254991 +- 123991 6 bad android-chrome@79cd82244a,chromium@575467 7241749 +- 107637 9 bad android-chrome@79cd82244a,chromium@575468 7294317 +- 122930 9 bad android-chrome@79cd82244a,chromium@575471 7287981 +- 149966 6 bad android-chrome@a84cb2f7c2 7191136 +- 101479 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=background.search.google 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/8940210600521798336 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 23