Issue metadata
Sign in to add a comment
|
5.6%-346.5% regression in system_health.memory_desktop at 476016:476334 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8977329051497419312
,
Jun 8 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : khushalsagar Commit : 4e1be6ae8914f0eeed1df004b74a467bcb93241b Date : Wed May 31 21:45:49 2017 Subject: cc: Enable perf testing for checker-imaging. Bisect Details Configuration: mac_10_11_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/browse_news/browse_news_flipboard Change : 339.01% | 13327221.3333 -> 58508027.8333 Revision Result N chromium@476015 13327221 +- 1372102 6 good chromium@476031 13077415 +- 2896.35 6 good chromium@476039 13327549 +- 1370312 6 good chromium@476040 13328211 +- 1372472 6 good chromium@476041 58450218 +- 402049 6 bad <-- chromium@476043 58518422 +- 632010 6 bad chromium@476046 59008743 +- 1862089 6 bad chromium@476077 58407103 +- 1699818 6 bad chromium@476139 58284511 +- 738829 6 bad chromium@476262 58508028 +- 317613 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.news.flipboard system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8977329051497419312 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5904428223168512 | 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 etienneb@chromium.org
, Jun 8 2017