Issue metadata
Sign in to add a comment
|
36.6% regression in system_health.memory_desktop at 459370:459418 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976339438711470112
,
Jun 19 2017
,
Jun 19 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_mini_8gb_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_media/browse_media_imgur Revision Result N chromium@459369 314174803 +- 336937122 21 good chromium@459418 290892914 +- 222252742 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=browse.media.imgur system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976339438711470112 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6090778868187136 | 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!
,
Jun 19 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976321079625754240
,
Jun 20 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: mac_10_12_mini_8gb_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/browse_media/browse_media_imgur Revision Result N chromium@459369 287769708 +- 213192685 21 good chromium@459418 289436645 +- 197666597 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=browse.media.imgur system_health.memory_desktop Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976321079625754240 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6090778868187136 | 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!
,
Jun 20 2017
,
Aug 17 2017
Issue 734628 has been merged into this issue.
,
Aug 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970983375793261120
,
Aug 17 2017
Looks like the regression could have occurred over a pretty wide range. Kicked the bisect off over a larger range.
,
Aug 18 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please 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:all_processes:reported_by_chrome:cc:effective_size_avg/browse_media/browse_media_imgur 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=browse.media.imgur 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/8970983375793261120 For feedback, file a bug with component Speed>Bisection
,
Aug 18 2017
Bisect didn't reproduce on a wider range. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by etienneb@chromium.org
, Jun 19 2017