Issue metadata
Sign in to add a comment
|
32% improvement in system_health.memory_mobile at 480313:480379 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974476323018300960
,
Jul 10 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_nexus6_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/background_search/background_search_google Change : 30.81% | 48763530.6667 -> 33740768.0 Revision Result N chromium@480312 48763531 +- 435128 6 good chromium@480329 48720523 +- 452433 6 good chromium@480338 48637920 +- 0.0 6 good chromium@480340 48700725 +- 343999 6 good chromium@480341 48771723 +- 464807 6 good chromium@480342 32543371 +- 2828333 6 bad <-- chromium@480346 32511968 +- 2076854 6 bad chromium@480379 33740768 +- 2086429 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 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8974476323018300960 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 10 2017