Issue metadata
Sign in to add a comment
|
1%-737.2% regression in system_health.memory_desktop at 407380:407382 |
||||||||||||||||||||
Issue descriptionThis was due to an infrastructure change: https://codereview.chromium.org/2161363004
,
Jul 25 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006153313150225376
,
Jul 25 2016
,
Jul 25 2016
=== Auto-CCing suspected CL author petrcermak@chromium.org === Hi petrcermak@chromium.org, the bisect results pointed to your CL below as possibly causing a regression. Please have a look at this info and see whether your CL be related. ===== BISECT JOB RESULTS ===== Status: completed ===== SUSPECTED CL(s) ===== Subject : [system-health] Tear down the browser after each story in system_health.memory_* Author : petrcermak Commit description: Rationale: Each story should be completely independent as it will allow us to compare the results from individual stories. As a result, it will be possible to compare/subtract the results from, e.g. LOAD:social:facebook and BROWSE:social:facebook. More importantly, there are literally hundreds of perf dashboard alerts each time we add a story to the SH story set. This should fix that. *** NOTE TO PERF SHERIFF *** This patch will definitely cause a lot of improvements and/or regressions in system_health.memory_desktop and system_health.memory_mobile benchmarks. This is expected. BUG=589726 CQ_INCLUDE_TRYBOTS=master.tryserver.chromium.perf:android_s5_perf_cq;master.tryserver.chromium.perf:linux_perf_cq;master.tryserver.chromium.perf:mac_retina_perf_cq;master.tryserver.chromium.perf:winx64_10_perf_cq Review-Url: https://codereview.chromium.org/2161363004 Cr-Commit-Position: refs/heads/master@{#407380} Commit : a30a0719cdc625d240ba75054fc0de1b9f826625 Date : Sun Jul 24 12:32:33 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@407379 224052 0.0 5 good chromium@407380 1875713 0.0 5 bad <-- Bisect job ran on: mac_retina_perf_bisect Bug ID: 631048 Test Command: src/tools/perf/run_benchmark -v --browser=release --output-format=chartjson --upload-results --also-run-disabled-tests system_health.memory_desktop Test Metric: load_social-memory:chrome:all_processes:reported_by_chrome:web_cache:effective_size_avg/load_social_vk Relative Change: 737.18% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_retina_perf_bisect/builds/1442 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006153313150225376 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=6317234314543104 | 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 25 2016