Issue metadata
Sign in to add a comment
|
2.1%-2.7% regression in memory.top_10_mobile_stress at 448837:448884 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988018679253244240
,
Feb 12 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_webview_nexus6_aosp_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:webview:all_processes:reported_by_chrome:v8:effective_size_avg/background/after_https_m_facebook_com_rihanna Revision Result N chromium@448836 6029520 +- 385044 21 good chromium@448884 6030230 +- 345185 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 memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988018679253244240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6341033127837696 | 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!
,
Feb 24 2017
metric has recovered.
,
Mar 11 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by majidvp@google.com
, Feb 10 2017