Issue metadata
Sign in to add a comment
|
2.2%-10.6% regression in system_health.memory_mobile at 489896:490338 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972177968460617296
,
Aug 4 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Helen Li Commit : 73f7cac54a1108eac07d5c7c3367f979a899a0bd Date : Thu Jul 27 14:57:57 2017 Subject: [wpr-go] Switch system_health_mobile.json to use go Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/background_search/background_search_google Change : 12.55% | 7775523.71429 -> 8539588.57143 Revision Result N chromium@489895 7775524 +- 30693.0 14 good chromium@489913 7773531 +- 31169.0 14 good chromium@489922 7774803 +- 32582.9 9 good chromium@489923 8271313 +- 1161020 6 bad <-- chromium@489924 8584879 +- 862899 6 bad chromium@489926 8371648 +- 1046068 6 bad chromium@489930 8230169 +- 2156989 21 bad chromium@489964 8539589 +- 1464199 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 --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/8972177968460617296 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 4 2017