Issue metadata
Sign in to add a comment
|
4.5% regression in system_health.memory_mobile at 1531227594:1531259369 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 13
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8941131239361679888
,
Jul 13
,
Jul 15
=== BISECT JOB RESULTS === Bisect was unable to run to completion Please try rerunning the bisect. If failures persist contact the team (see below) and report the error. Bisect Details Configuration: go-phone-1024-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/browse_social/browse_social_facebook_infinite_scroll Change : 2.53% | 22893138.0 -> 23472000.8889 Revision Result N android-chrome@96555ff9c3 22893138 +- 378025 14 good android-chrome@96555ff9c3,chromium@573466 22761099 +- 279051 6 good android-chrome@96555ff9c3,chromium@573545 22854213 +- 113512 6 good android-chrome@0c23a72c68 23403130 +- 380451 14 bad android-chrome@7b94b395a3 23349148 +- 512049 21 bad android-chrome@cd63705090 23443428 +- 356454 14 bad android-chrome@cb4b582a48 23472001 +- 529660 9 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-chrome --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=browse.social.facebook.infinite.scroll system_health.memory_mobile More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8941131239361679888 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 13