Issue metadata
Sign in to add a comment
|
1.2%-7% regression in system_health.memory_mobile at 474671:474922 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
May 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978200404896622928
,
May 30 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_shopping/browse_shopping_avito Revision Result N chromium@474752 47279749 +- 9516382 21 good chromium@474857 50131324 +- 11783732 21 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.shopping.avito system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978200404896622928 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6378701966540800 | 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 30 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8978193423485378784
,
May 30 2017
=== BISECT JOB RESULTS === Perf regression found but unable to narrow commit range Build failures prevented the bisect from narrowing the range further. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:malloc:effective_size_avg/browse_shopping/browse_shopping_avito Change : 7.66% | 47357157.4286 -> 50983064.2857 Suspected Commit Range 2 commits in range https://chromium.googlesource.com/chromium/src/+log/a283fb63e50aacdb88401e8d1f4b05f15256b705..61b2c92224f1bb6db51b0d7b9a84a08dd451f658 Revision Result N chromium@474752 47357157 +- 7153997 14 good chromium@474806 48121424 +- 8372080 14 good chromium@474831 48528999 +- 11538821 21 good chromium@474837 48539584 +- 12436898 21 good chromium@474838 --- --- build failure chromium@474839 51196442 +- 8752673 14 bad chromium@474845 51695766 +- 5229073 9 bad chromium@474857 50983064 +- 10271947 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.shopping.avito system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8978193423485378784 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6378701966540800 | 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 31 2017
chromium@474837 48539584 +- 12436898 21 good chromium@474838 --- --- build failure chromium@474839 51196442 +- 8752673 14 bad Let me assign dcheng@, author of chromium@474839. https://chromium.googlesource.com/chromium/src/+/61b2c92224f1bb6db51b0d7b9a84a08dd451f658
,
Jun 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8976996027614896176
,
Jun 13 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : fdoray Commit : 6eb5c1eb647e1709b4b03ae5148f8c03daea03fb Date : Thu May 25 19:51:13 2017 Subject: Update TaskTraits in v8_platform.cc. Bisect Details Configuration: android_nexus5X_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/background_media/background_media_imgur Change : 5.92% | 43692100.0 -> 46279577.3333 Revision Result N chromium@474000 43692100 +- 627408 6 good chromium@474500 44188569 +- 887871 6 good chromium@474750 44077977 +- 698561 6 good chromium@474758 44042991 +- 1086153 6 good chromium@474760 43805935 +- 332419 6 good chromium@474761 43957828 +- 811034 6 good chromium@474762 45213935 +- 874621 9 bad <-- chromium@474766 45590937 +- 695471 6 bad chromium@474782 45508505 +- 576947 6 bad chromium@474813 45539396 +- 292759 6 bad chromium@474875 45516868 +- 457893 6 bad chromium@475000 46279577 +- 895715 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=background.media.imgur system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8976996027614896176 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=6395857575870464 | 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! |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by toyoshim@chromium.org
, May 30 2017