Issue metadata
Sign in to add a comment
|
3.7%-7.1% regression in system_health.memory_mobile at 406043:406090 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 21 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006522728709803632
,
Jul 21 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406042 50945317 239770 12 good chromium@406090 50886608 355948 12 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 630274 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile Test Metric: load_news-memory:chrome:all_processes:reported_by_os:system_memory:native_heap:private_dirty_size_avg/load_news_hackernews Relative Change: 0.06% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1905 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006522728709803632 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6382545063641088 | 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 Tests>AutoBisect. Thank you!
,
Jul 21 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006501852503715024
,
Jul 21 2016
,
Jul 22 2016
===== BISECT JOB RESULTS ===== Status: completed === Bisection aborted === The bisect was aborted because The metric values for the initial "good" and "bad" revisions do not represent a clear regression. Please contact the the team (see below) if you believe this is in error. === Warnings === The following warnings were raised by the bisect job: * Bisect failed to reproduce the regression with enough confidence. ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406042 1384860 16542.6 12 good chromium@406090 1381527 12885.0 12 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 630274 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile Test Metric: load_news-memory:chrome:all_processes:reported_by_chrome:sqlite:effective_size_avg/load_news_cnn Relative Change: 0.57% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1906 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006501852503715024 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5672363127996416 | 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 Tests>AutoBisect. Thank you!
,
Jul 25 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006154774634419872
,
Jul 26 2016
===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [system-health] Run all SH stories in memory benchmarks Author : petrcermak Commit description: This patch modifies SH memory benchmarks (system_health.memory_desktop and system_health.memory_mobile) to run all SH stories: - load:* (already running) - browse:* (NEW) As a result, all SH stories will also run in the SH smoke test on the Chromium CQ (benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.*). *** NOTE TO SHERIFF *** This patch is very likely to cause failures in the System Health benchmarks (perf waterfall) and smoke tests (regular CQ). Please contact me before reverting. BUG=589726 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:mac_retina_perf_cq Review-Url: https://codereview.chromium.org/2159733002 Cr-Commit-Position: refs/heads/master@{#406309} Commit : 77952f99e4ae203b6b57005ce9e3476895426b96 Date : Tue Jul 19 18:03:07 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@406001 46370191 210588 5 good chromium@406211 47026764 78241.5 5 good chromium@406264 47228409 99027.8 5 good chromium@406290 47090969 131683 5 good chromium@406303 47162310 87846.2 5 good chromium@406307 46897557 176143 5 good chromium@406308 47065678 75895.2 5 good chromium@406309 48290803 71376.7 5 bad <-- chromium@406310 48241109 81735.5 5 bad chromium@406316 48338162 85960.6 5 bad chromium@406420 48330672 206697 5 bad Bisect job ran on: android_nexus9_perf_bisect Bug ID: 630274 Test Command: src/tools/perf/run_benchmark -v --browser=android-chromium --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_mobile Test Metric: load_search-memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/load_search_ebay Relative Change: 4.23% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus9_perf_bisect/builds/1912 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006154774634419872 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5770271101812736 | 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 Tests>AutoBisect. Thank you!
,
Aug 30 2016
,
Aug 30 2016
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by petrcermak@chromium.org
, Jul 21 2016