Issue metadata
Sign in to add a comment
|
1.9%-3% regression in memory.top_10_mobile at 480313:480379 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 21 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976142186152131376
,
Jun 22 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Yutaka Hirano Commit : 84047549ac37bab70d7306566c912e59131f3e1f Date : Mon Jun 19 04:16:15 2017 Subject: [Loading] Save one post-task when the data pipe is ready on arrival Bisect Details Configuration: android_one_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/foreground/http_yandex_ru_touchsearch_text_science Change : 3.00% | 2182636.0 -> 2248172.0 Revision Result N chromium@480312 2182636 +- 0.0 6 good chromium@480330 2182636 +- 0.0 6 good chromium@480339 2182636 +- 0.0 6 good chromium@480341 2182636 +- 0.0 6 good chromium@480342 2248172 +- 0.0 6 bad <-- chromium@480344 2248172 +- 0.0 6 bad chromium@480348 2248172 +- 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976142186152131376 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4827651182690304 | 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 lanwei@chromium.org
, Jun 21 2017