Issue metadata
Sign in to add a comment
|
1.1% regression in memory.top_10_mobile at 485931:485998 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 24 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8973192048493435200
,
Jul 24 2017
,
Jul 24 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_nexus7_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/foreground/https_m_facebook_com_rihanna Change : 0.62% | 20323397.8571 -> 20449815.8571 Revision Result N chromium@485930 20323398 +- 570916 21 good chromium@485933 20296492 +- 418261 9 good chromium@485934 20269001 +- 454872 9 good chromium@485935 20498915 +- 233512 9 bad <-- chromium@485939 20437392 +- 433384 14 bad chromium@485948 20458090 +- 190692 9 bad chromium@485964 20453371 +- 443428 14 bad chromium@485998 20449816 +- 507438 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/8973192048493435200 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