Issue metadata
Sign in to add a comment
|
1% regression in memory.top_10_mobile at 485916:486005 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973191950594905584
,
Jul 24 2017
,
Jul 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Ken Rockot Commit : 474df01407e5d38c85364ae4d1709b8d9af16f16 Date : Wed Jul 12 13:28:56 2017 Subject: Mojo C++ Bindings: Lazy Serialization Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/https_www_google_co_uk_hl_en_q_science Change : 0.90% | 19897890.1429 -> 20076567.5714 Revision Result N chromium@485915 19897890 +- 574451 14 good chromium@485929 19907597 +- 591751 21 good chromium@485933 19908874 +- 316290 9 good chromium@485934 19856056 +- 136521 6 good chromium@485935 20108931 +- 339804 9 bad <-- chromium@485939 20048566 +- 550428 21 bad chromium@485961 20029259 +- 473465 21 bad chromium@486005 20076568 +- 358245 14 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 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8973191950594905584 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 24 2017