Issue metadata
Sign in to add a comment
|
1%-25.5% regression in system_health.memory_mobile at 463521:463601 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Apr 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982021505312246912
,
Apr 18 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : delphick Commit : d8ade60fbe0ea954ecd5f186c36e6d0ac045c28c Date : Tue Apr 11 09:56:28 2017 Subject: No longer clamp setTimeout(..., 0) to 1ms. Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/background_search/background_search_google Change : 25.38% | 138992.0 -> 174268.0 Revision Result N chromium@463547 138992 +- 0.0 6 good chromium@463572 138992 +- 0.0 6 good chromium@463585 138992 +- 0.0 6 good chromium@463588 138992 +- 0.0 6 good chromium@463590 138992 +- 0.0 6 good chromium@463591 174268 +- 0.0 6 bad <-- chromium@463597 174268 +- 0.0 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=background.search.google system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982021505312246912 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5775792165879808 | 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 benhenry@google.com
, Apr 18 2017