Issue metadata
Sign in to add a comment
|
8%-13.8% regression in system_health.memory_desktop at 491274:491412 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972178336096700528
,
Aug 4 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Michael Lippautz Commit : c56ae86ad852cd0b7af931e42f7ee29308b79574 Date : Wed Aug 02 14:02:56 2017 Subject: Keep WorkerGlobalScope wrapper alive as long as its context is alive Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_news/load_news_qq Change : 12.44% | 119589546.667 -> 134460757.333 Revision Result N chromium@491314 119589547 +- 8979468 6 good chromium@491339 122036224 +- 8388608 6 good chromium@491351 118366208 +- 5190186 6 good chromium@491357 120463360 +- 7985717 6 good chromium@491360 118628352 +- 7732137 6 good chromium@491362 121162411 +- 5962456 6 good chromium@491363 136820053 +- 9221112 6 bad <-- chromium@491412 134460757 +- 3431317 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=release_x64 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.news.qq 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/8972178336096700528 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 4 2017