Issue metadata
Sign in to add a comment
|
5.7% regression in memory.desktop at 496676:496753 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 28 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969998882600030832
,
Aug 28 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Sami Kyostila Commit : be262cd3ee73975ced4e339d630b18f3e7e4145b Date : Wed Aug 23 18:53:03 2017 Subject: perf: Disable native heap profiling in memory benchmarks Bisect Details Configuration: winx64_10_perf_bisect Benchmark : memory.desktop Metric : memory:chrome:all_processes:reported_by_os:system_memory:proportional_resident_size_avg/TrivialWebGLPageSharedPageState Change : 6.03% | 138488857.0 -> 146837289.0 Revision Result N chromium@496675 138488857 +- 4682647 6 good chromium@496714 138455718 +- 2985803 6 good chromium@496734 138711533 +- 2205549 6 good chromium@496744 138455522 +- 535346 6 good chromium@496749 137810738 +- 1601715 6 good chromium@496750 137465793 +- 3839065 6 good chromium@496751 144899572 +- 2774597 6 bad <-- chromium@496753 146837289 +- 2146611 6 bad 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=TrivialWebGLPageSharedPageState memory.desktop More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969998882600030832 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 28 2017