Issue metadata
Sign in to add a comment
|
7.1% regression in system_health.memory_desktop at 496705:496822 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Sep 4 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969399250606875008
,
Sep 4 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: mac_air_perf_bisect Benchmark : system_health.memory_desktop Metric : memory:chrome:renderer_processes:reported_by_chrome:v8:heap:effective_size_avg/load_tools/load_tools_docs Change : 10.47% | 66940986.6667 -> 73946413.3333 Revision Result N chromium@496704 66940987 +- 808195 6 good chromium@496734 67200016 +- 548405 6 good chromium@496749 66872712 +- 1223525 6 good chromium@496750 66780784 +- 1039283 6 good chromium@496751 74739483 +- 3201955 6 bad <-- chromium@496753 74261623 +- 7852929 6 bad chromium@496756 73928027 +- 3185696 6 bad chromium@496763 73569288 +- 4155256 6 bad chromium@496822 73946413 +- 3442993 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 --output-format=chartjson --upload-results --pageset-repeat=1 --also-run-disabled-tests --story-filter=load.tools.docs 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/8969399250606875008 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Sep 4 2017