Issue metadata
Sign in to add a comment
|
1.7%-136.5% regression in system_health.memory_mobile at 514279:514432 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 8 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963471578000945904
,
Nov 8 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Nate Chapin Commit : 1aec1a92fb786cae0a24ff2b22d4858d4486252e Date : Mon Nov 06 23:47:59 2017 Subject: Make script cache hits async Bisect Details Configuration: winx64_10_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:all_processes:reported_by_chrome:cc:effective_size_avg/load_media/load_media_imgur Change : 104.93% | 40319017.7778 -> 82625236.4444 Revision Result N chromium@514278 40319018 +- 59164019 9 good chromium@514290 44047288 +- 40308265 6 good chromium@514296 37812493 +- 33207216 6 good chromium@514298 39621560 +- 42863873 6 good chromium@514299 81484728 +- 72958039 9 bad <-- chromium@514302 101028109 +- 29550279 6 bad chromium@514326 92375309 +- 28069889 6 bad chromium@514374 82625236 +- 68790477 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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.media.imgur system_health.memory_desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8963471578000945904 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 8 2017