system_health.memory_desktop: potential regression in 456689-456784 |
||
Issue descriptionEtienne discovered what appears to be a large regression in this range. We currently don't alert this measurement. Bisect 1: https://chromeperf.appspot.com/buildbucket_job_status/8983683526284280064 https://chromeperf.appspot.com/report?sid=cf662d332e473cab3797cec5d312f08b68383df1e21aa96cce3eedcd7da88489&start_rev=416456&end_rev=460688
,
Mar 30 2017
Started another bisect, this time only using browse_news.
,
Mar 30 2017
,
Mar 31 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: eacc38c7d843ef2d60597070557ce015c451d616 bad_revision : 08614915649c30c0278a9b154825e370b819a6de If failures persist contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_chrome:malloc:allocated_objects_size_avg/browse_news Revision Result N chromium@456689 157845455 +- 4806590 6 good chromium@456737 157858165 +- 3614949 6 good chromium@456761 157650745 +- 3230282 6 good chromium@456767 207135891 +- 5364956 6 bad chromium@456773 206580119 +- 4734693 6 bad chromium@456784 207686118 +- 6114315 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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8983670611225516144 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5126189993164800 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982651952801027728
,
Apr 12 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: eacc38c7d843ef2d60597070557ce015c451d616 bad_revision : 08614915649c30c0278a9b154825e370b819a6de If failures persist contact the team (see below) and report the error. Bisect Details Configuration: winx64_10_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_chrome:malloc:allocated_objects_size_avg/browse_news Revision Result N chromium@456689 157165060 +- 1001413 6 good chromium@456737 156954889 +- 522632 6 good chromium@456761 158482351 +- 4657590 6 good chromium@456767 208862943 +- 7004936 6 bad chromium@456773 207292699 +- 5259929 6 bad chromium@456784 207573748 +- 5885147 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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982651952801027728 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5126189993164800 | O O | Visit http://www.chromium.org/developers/speed-infra/perf-bug-faq | X | for more information addressing perf regression bugs. For feedback, | / \ | file a bug with component Speed>Bisection. Thank you!
,
Jan 10
Archiving P3s older than 1 year with no owner or component. |
||
►
Sign in to add a comment |
||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Mar 30 2017