Issue metadata
Sign in to add a comment
|
1.8%-9% regression in system_health.memory_mobile at 450326:450531 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Feb 16 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987514922027241168
,
Feb 16 2017
=== Auto-CCing suspected CL author yosin@chromium.org === Hi yosin@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : yosin Commit : d892f9592860691ae9a782c12260c94ed6bd1a63 Date : Tue Feb 14 15:56:00 2017 Subject: Make FrameSelection to hold non-canonicalized DOM positions Bisect Details Configuration: android_nexus6_perf_bisect Benchmark : memory.top_10_mobile Metric : memory:chrome:all_processes:reported_by_chrome:skia:effective_size_avg/foreground/https_m_facebook_com_rihanna Change : 8.98% | 282912.0 -> 308328.0 Revision Result N chromium@450325 282912 +- 0.0 6 good chromium@450352 285736 +- 23962.4 9 good chromium@450366 291989 +- 45566.9 14 good chromium@450368 287148 +- 23201.5 6 good chromium@450369 282912 +- 0.0 6 good chromium@450370 308328 +- 0.0 9 bad <-- chromium@450373 308328 +- 0.0 9 bad chromium@450379 308328 +- 0.0 9 bad chromium@450432 308328 +- 0.0 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 memory.top_10_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987514922027241168 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5029424539369472 | 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!
,
Feb 17 2017
,
Feb 17 2017
,
Feb 17 2017
,
Feb 18 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8987322895952902368
,
Feb 18 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: android_one_perf_bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_os:system_memory:native_heap:proportional_resident_size_avg/browse_news/browse_news_reddit Revision Result N chromium@451268 37819761 +- 1094119 21 good chromium@451272 37871887 +- 850836 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.news.reddit system_health.memory_mobile Debug Info https://chromeperf.appspot.com/buildbucket_job_status/8987322895952902368 Is this bisect wrong? https://chromeperf.appspot.com/bad_bisect?try_job_id=5287032785469440 | 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!
,
Apr 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8982624380307849888 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by alexclarke@chromium.org
, Feb 16 2017