Issue metadata
Sign in to add a comment
|
258.6% regression in system_health.memory_mobile at 525759:525841 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Dec 22 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8959471944730315184
,
Dec 23 2017
=== BISECT JOB RESULTS === Perf regression found but unable to continue Bisect was stopped because a commit couldn't be classified as either good or bad. Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:webview:all_processes:reported_by_chrome:gpu:effective_size_avg/browse_social/browse_social_facebook_infinite_scroll Revision Result N chromium@525758 135168 +- 0.0 21 good chromium@525800 135168 +- 0.0 21 good chromium@525821 135168 +- 0.0 21 good chromium@525831 185100 +- 1023305 21 unknown chromium@525841 484693 +- 2265183 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=browse.social.facebook.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/8959471944730315184 For feedback, file a bug with component Speed>Bisection
,
Jan 23 2018
Issue 797376 has been merged into this issue.
,
Jan 23 2018
📍 Pinpoint job started. https://pinpoint-dot-chromeperf.appspot.com/job/1283122c840000
,
Jan 24 2018
📍 Couldn't reproduce a difference. https://pinpoint-dot-chromeperf.appspot.com/job/1283122c840000
,
Mar 2 2018
This recovered. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Dec 22 2017