Issue metadata
Sign in to add a comment
|
1.3%-351.4% regression in system_health.memory_mobile at 405140:405221 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 14 2016
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/9007147017362422128
,
Jul 14 2016
===== 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@405208 1727693 8394.3 5 good chromium@405211 1726054 4670.16 5 good chromium@405212 7834829 14306.7 5 bad <-- chromium@405213 7831552 19211.9 5 bad chromium@405214 7834010 12150.7 5 bad chromium@405220 7836467 4486.94 5 bad Bisect job ran on: android_nexus5_perf_bisect Bug ID: 628253 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_social-memory:chrome:all_processes:reported_by_os:system_memory:ashmem:private_dirty_size_avg/load_social_twitter Relative Change: 353.58% Score: 99.9 Buildbot stdio: http://build.chromium.org/p/tryserver.chromium.perf/builders/android_nexus5_perf_bisect/builds/3834 Job details: https://chromeperf.appspot.com/buildbucket_job_status/9007147017362422128 Not what you expected? We'll investigate and get back to you! https://chromeperf.appspot.com/bad_bisect?try_job_id=5845880276516864 | 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