Issue metadata
Sign in to add a comment
|
1%-62.4% regression in system_health.memory_mobile at 464071:464717 |
||||||||||||||||||||
Issue descriptionGraphs to come. Clearly a regression as none of the ref builds are also regressing.
,
Apr 17 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982028569512560416
,
Apr 18 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/background_news/background_news_nytimes Revision Result N chromium@464072 15206107 +- 596547 14 good chromium@464717 24540891 +- 690020 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.news.nytimes system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8982028569512560416 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5843295562891264 | 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 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981937217974047088
,
Apr 19 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus7_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/background_news/background_news_nytimes Revision Result N chromium@464072 15173047 +- 533978 14 good chromium@464717 24517193 +- 1007343 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.news.nytimes system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981937217974047088 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5843295562891264 | 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 20 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981755083062997520
,
Apr 21 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/background_news/background_news_nytimes Revision Result N chromium@464070 25131886 +- 85806.8 14 good chromium@464717 35715950 +- 126304 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.news.nytimes system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981755083062997520 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5843295562891264 | 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 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8981030183400309392
,
Apr 30 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_social/browse_social_twitter Revision Result N chromium@464070 58458112 +- 92681.9 14 good chromium@464717 77042834 +- 9656828 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=browse.social.twitter system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8981030183400309392 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5843295562891264 | 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!
,
May 15 2017
+simonhatch these are some large-ish regressions, any idea why bisects are failing?
,
May 15 2017
Looks like it's hitting the 24 hour limit running the test. Gathering the reference values runs fine and repro's a large regression, but it can't find an mid point cl that's working before hitting 24 hr limit, all failing. In cases like this where the test may have been broken in the range, the bisect can't do much until we get functionality like optionally patching in a fix, which is a feature Pinpoint will support.
,
May 23 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978781241617157664
,
May 25 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_social/browse_social_twitter Revision Result N chromium@464070 64892298 +- 35115667 13 good chromium@464717 78917339 +- 9265001 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=browse.social.twitter system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978781241617157664 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5593517293830144 | 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!
,
May 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978661511443513328
,
May 26 2017
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: android_nexus5_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:gpu_memory:proportional_resident_size_avg/browse_social/browse_social_twitter Revision Result N chromium@464070 60238994 +- 23289822 14 good chromium@464717 75713615 +- 20844506 13 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=browse.social.twitter system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978661511443513328 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5593517293830144 | 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 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976998606313197824
,
Jun 12 2017
=== Auto-CCing suspected CL author jbauman@chromium.org === Hi jbauman@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : jbauman Commit : 7c2bb41a8275988ed20cbf8f5dbaba08a0f9f222 Date : Thu Apr 13 23:18:51 2017 Subject: Do additional blit and Present on first draw to overlay. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:java_heap:proportional_resident_size_avg/load_news/load_news_flipboard Change : 9.27% | 13467648.0 -> 14716757.3333 Revision Result N chromium@464500 13467648 +- 152297 6 good chromium@464600 13733888 +- 194463 6 good chromium@464601 16273920 +- 404841 6 bad <-- chromium@464602 15610197 +- 285876 6 bad chromium@464604 15144277 +- 395117 6 bad chromium@464607 15721131 +- 498474 6 bad chromium@464613 15412395 +- 493220 6 bad chromium@464625 15026347 +- 172132 6 bad chromium@464650 14932309 +- 184756 6 bad chromium@464700 14716757 +- 159681 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 --story-filter=load.news.flipboard system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976998606313197824 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=4988094131994624 | 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 14 2017
My change is windows-only.
,
Jun 14 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976796432837521728
,
Jun 16 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/load_media/load_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=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.imgur system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976796432837521728 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5105445791858688 | 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 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976615531838372256
,
Jun 18 2017
=== BISECT JOB RESULTS === NO Perf regression found, tests failed to produce values Bisect Details Configuration: android_webview_arm64_aosp_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:java_heap:effective_size_avg/load_media/load_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=android-webview --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.imgur system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976615531838372256 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5105445791858688 | 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!
,
Jul 19 2017
,
Jul 27 2017
This is shipped and too old to be actionable. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by benhenry@google.com
, Apr 17 2017