Issue metadata
Sign in to add a comment
|
1.9% regression in memory.top_10_mobile at 493219:493555 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970272881287963152
,
Aug 26 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: INFRA_FAILURE The bisect was able to narrow the range, you can try running with: good_revision: bb022357740c88dde09d3d2de6fd364c515714c2 bad_revision : 0c1a638978372a5b7982247363de73d61f6d6faa If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_one_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/foreground/http_search_yahoo_com_search__ylt_p_google Revision Result N chromium@493218 4873714 +- 47155.4 6 good chromium@493303 4885190 +- 56594.2 6 good chromium@493345 4891950 +- 111627 14 good chromium@493352 5042227 +- 330659 6 bad chromium@493366 4906376 +- 101701 14 bad chromium@493387 4968689 +- 52558.6 6 bad chromium@493555 4973552 +- 23875.5 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 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8970272881287963152 For feedback, file a bug with component Speed>Bisection
,
Sep 21 2017
We reduced the thresholds for alerting, this is below them. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 25 2017