Issue metadata
Sign in to add a comment
|
1.2%-662.5% regression in system_health.memory_mobile at 405195:405220 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 14 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007145407286242016
,
Jul 14 2016
=== Auto-CCing suspected CL author ulan@chromium.org === Hi ulan@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 : Add benchmark that imitates news reading. Author : ulan Commit description: Each story in the benchmark does the following: 1. Load the main page. 2. Open and scroll the first news item. 3. Go back to the main page and scroll it. 4. Open and scroll the second news item. 5. Go back to the main page and scroll it. 6. etc. This workflow is interesting because it is close to real world and generates a lot of garbage by creating and discarding pages. A couple of websites crash with OOM on svelte device, so by tracking and optimizing for this benchmark we can improve user experience on low-memory devices. *** NOTE TO SHERRIF *** Regressions are expected in system_health.memory_mobile and system_health.memory_desktop for the following stories: - load:news:cnn - load:social:facebook - load:news:qq - load:news:reddit - load:social:twitter If there are failing tests in form of benchmarks.system_health_smoke_test.SystemHealthBenchmarkSmokeTest.* please do not revert this CL but instead disabling failing test by adding them into the _DISABLE_TESTS list in tools/perf/benchmarks/system_health_smoke_test.py BUG=589726 CQ_INCLUDE_TRYBOTS=tryserver.chromium.perf:android_s5_perf_cq;tryserver.chromium.perf:mac_retina_perf_cq Review-Url: https://codereview.chromium.org/2118293002 Cr-Commit-Position: refs/heads/master@{#405212} Commit : 5b1847df818e5be4592e9a6ac4832350bb663023 Date : Wed Jul 13 17:39:28 2016 ===== TESTED REVISIONS ===== Revision Mean Std Dev N Good? chromium@405211 315392 6476.34 5 good chromium@405212 1532723 6730.41 5 bad <-- chromium@405213 1699021 378281 5 bad chromium@405214 1703936 382565 5 bad chromium@405216 1873510 471508 5 bad chromium@405220 1872691 462906 5 bad Bisect job ran on: android_nexus5X_perf_bisect Bug ID: 628268 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:ashmem:private_dirty_size_avg/load_news_qq Relative Change: 493.77% Score: 99.8 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5X_perf_bisect/builds/337 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007145407286242016 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5867909029560320 | 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 15 2016
The regression is due to changing stories in the SH storyset.
,
Jul 18 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006799800886216576
,
Jul 18 2016
,
Jul 22 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9006394949155130608
,
Jul 23 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@405120 1711738 66086.9 8 good chromium@405184 1736646 62237.7 5 bad Bisect job ran on: mac_hdd_perf_bisect Bug ID: 628268 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:sqlite:effective_size_avg/load_social_twitter Relative Change: 1.14% Score: 0 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/mac_hdd_perf_bisect/builds/660 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9006394949155130608 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5298611819118592 | 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 14 2016