Issue metadata
Sign in to add a comment
|
1.1% regression in memory.top_10_mobile at 467939:467974 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 2 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8980681756643265840
,
May 3 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : delphick Commit : c41d3c785c5179a38e54c6c80ea63d56cc7cfd12 Date : Fri Apr 28 11:50:09 2017 Subject: Restore one millisecond minimum timeout for setTimeout. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background/after_http_www_amazon_com_gp_aw_s_k_nexus Change : 1.09% | 162171.555556 -> 163736.0 Revision Result N chromium@467938 162172 +- 1659.34 9 good chromium@467956 162479 +- 2974.94 14 good chromium@467961 161976 +- 0.0 6 good chromium@467962 163736 +- 0.0 6 bad <-- chromium@467963 163736 +- 0.0 6 bad chromium@467965 163736 +- 0.0 6 bad chromium@467974 163736 +- 0.0 9 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 Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8980681756643265840 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6101385147318272 | 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