Issue metadata
Sign in to add a comment
|
3.4%-5.9% regression in system_health.memory_mobile at 1527515353:1527535866 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jun 7 2018
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8944399897130148800
,
Jun 9 2018
=== BISECT JOB RESULTS === Bisect was unable to run to completion Error: TIMEOUT The bisect was able to narrow the range, you can try running with: good_revision: 722d4fc08892853358878a612b91d1025bda2105 bad_revision : 4c136b3e1c68e1d47550e48ba9031696e37198d6 If failures persist contact the team (see below) and report the error. Bisect Details Configuration: clankium-low-end-phone-perf-bisect Benchmark : system_health.memory_mobile Metric : memory:chrome:all_processes:reported_by_chrome:v8:effective_size_avg/load_media/load_media_facebook_photos Change : 6.99% | 3297071.55556 -> 3527635.11111 Revision Result N android-chrome@3e8ad5c58a 3297072 +- 17821.5 9 good android-chrome@722d4fc088 3300370 +- 12471.6 9 good android-chrome@4c136b3e1c 3527635 +- 154986 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=load.media.facebook.photos 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/8944399897130148800 For feedback, file a bug with component Speed>Bisection
,
Jun 11 2018
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jun 7 2018