Issue metadata
Sign in to add a comment
|
1.6%-6.6% regression in system_health.memory_mobile at 473863:474136 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978194847654710800
,
May 30 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : danakj Commit : 4188df86ebb468a6723b1c5855c75be8e4ae91a3 Date : Tue May 23 20:05:29 2017 Subject: Avoid quickReject() when rastering a cc::DrawingDisplayItem. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_tools/browse_tools_maps Change : 6.68% | 65529017.3333 -> 69906052.0 Revision Result N chromium@473862 65529017 +- 78518.0 6 good chromium@473994 65533860 +- 107595 6 good chromium@474011 65512015 +- 63863.2 6 good chromium@474013 65546809 +- 55051.6 6 good chromium@474014 69871172 +- 88315.3 6 bad <-- chromium@474015 69931951 +- 341504 6 bad chromium@474019 69908868 +- 268640 6 bad chromium@474027 69935780 +- 314817 6 bad chromium@474060 69879279 +- 104833 6 bad chromium@474126 69906052 +- 251783 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.tools.maps system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978194847654710800 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5219173136859136 | 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 toyoshim@chromium.org
, May 30 2017