Issue metadata
Sign in to add a comment
|
3.5% regression in memory.top_10_mobile_stress at 448522:448574 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 9 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8988180921017640272
,
Feb 9 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : ssid Commit : efed310cc305f0d89f9d1aa49fb5e0d4ec9ff2cd Date : Tue Feb 07 05:29:58 2017 Subject: [memory-infra] Make client discardable segments non-weak Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile_stress Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_www_baidu_com_s_word_google Change : 4.17% | 25115620.0 -> 26162300.0 Revision Result N chromium@448521 25115620 +- 0.0 6 good chromium@448548 25115620 +- 0.0 6 good chromium@448552 25142295 +- 146103 6 good chromium@448553 25142295 +- 146103 6 good chromium@448554 26108319 +- 591336 6 bad <-- chromium@448555 26054337 +- 295668 6 bad chromium@448562 26000356 +- 0.0 6 bad chromium@448574 26162300 +- 605939 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 memory.top_10_mobile_stress Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8988180921017640272 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4931330808217600 | 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 briander...@chromium.org
, Feb 9 2017