Issue metadata
Sign in to add a comment
|
9.3% regression in system_health.memory_desktop at 503428:503498 |
||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8966721483779537920
,
Oct 4 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: 6a8d2a721d7d281dba0bb87fbd1d0e9358d6ce7d bad_revision : abadaa9269ad0ede8d1dec0ba672c9f93bb8f689 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: mac_10_12_mini_8gb_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:allocated_objects_size_avg/load_tools/load_tools_docs Revision Result N chromium@503453 57485377 +- 18796663 21 good chromium@503483 56711075 +- 14221875 14 good chromium@503491 57954368 +- 15189163 14 good chromium@503495 64408228 +- 8253956 6 bad chromium@503498 63358465 +- 20901025 14 bad chromium@503513 63853503 +- 15350891 9 bad chromium@503572 65010190 +- 33261911 21 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=release --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.docs system_health.memory_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8966721483779537920 For feedback, file a bug with component Speed>Bisection
,
Aug 2
,
Aug 2
|
|||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 23 2017