Issue metadata
Sign in to add a comment
|
3% regression in system_health.memory_mobile at 467336:467478 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980683684211656224
,
May 2 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : ben Commit : b932d5ad0c349295c9d10de144f9358370e57b5c Date : Wed Apr 26 19:40:13 2017 Subject: Implement Connector::ApplySpec() & use to enforce navigation:frame. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_shopping/browse_shopping_amazon Change : 3.81% | 23822093.3333 -> 24730552.0 Revision Result N chromium@467335 23822093 +- 346393 6 good chromium@467407 23976755 +- 280802 6 good chromium@467412 23887421 +- 395226 6 good chromium@467414 23830994 +- 411534 6 good chromium@467415 24747449 +- 191516 6 bad <-- chromium@467416 24736041 +- 316728 6 bad chromium@467425 24799931 +- 208769 6 bad chromium@467443 24632775 +- 209713 6 bad chromium@467478 24730552 +- 389180 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-chromium --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.shopping.amazon system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980683684211656224 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5817361912823808 | 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! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nzolghadr@chromium.org
, May 2 2017