Issue metadata
Sign in to add a comment
|
2975%-5175% regression in system_health.memory_mobile at 452799:452857 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Mar 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8986217083397226480
,
Mar 2 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yhirano Commit : 865407349e3755b33d6db5642501f88c8fb7784d Date : Fri Feb 24 14:43:30 2017 Subject: Do not reuse a loading resource associated with another fetcher 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/load_social/load_social_tumblr Change : 5175.00% | 131072.0 -> 6914048.0 Revision Result N chromium@452819 131072 +- 0.0 6 good chromium@452822 131072 +- 0.0 6 good chromium@452823 6914048 +- 0.0 6 bad <-- chromium@452824 6914048 +- 0.0 6 bad chromium@452828 6914048 +- 0.0 6 bad chromium@452838 6914048 +- 0.0 6 bad chromium@452857 6914048 +- 0.0 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=load.social.tumblr system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8986217083397226480 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5640288971784192 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Mar 11 2017
,
Mar 11 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by sullivan@chromium.org
, Mar 2 2017