Issue metadata
Sign in to add a comment
|
6.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/8980683654213390352
,
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_news/browse_news_toi Change : 6.69% | 37402563.6667 -> 39904854.3333 Revision Result N chromium@467335 37402564 +- 801350 6 good chromium@467407 37254299 +- 1710892 6 good chromium@467412 37457834 +- 537915 6 good chromium@467414 37124352 +- 1669018 6 good chromium@467415 39693660 +- 414620 6 bad <-- chromium@467416 39877531 +- 790378 6 bad chromium@467425 39987150 +- 1174700 6 bad chromium@467443 40048507 +- 586275 6 bad chromium@467478 39904854 +- 1306170 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.news.toi system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980683654213390352 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5269556953612288 | 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