Issue metadata
Sign in to add a comment
|
9.4%-27.9% regression in system_health.memory_desktop at 490746:490774 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 3 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8972297651260244992
,
Aug 3 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Helen Li Commit : 05ee1dbfaf0aa7c03b9ea2040f0345277042d0f1 Date : Mon Jul 31 13:24:01 2017 Subject: [wpr-go] Switch system_health_desktop.json to use go 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_9gag Change : 27.85% | 9518229.33333 -> 12169108.0 Revision Result N chromium@490745 9518229 +- 9004.99 6 good chromium@490749 9535979 +- 89066.4 6 good chromium@490750 9538027 +- 87017.9 6 good chromium@490751 12189588 +- 85330.6 6 bad <-- chromium@490753 12188223 +- 87017.9 6 bad chromium@490760 12188223 +- 86824.9 6 bad chromium@490774 12169108 +- 8192.0 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.media.9gag 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/8972297651260244992 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 3 2017