Issue metadata
Sign in to add a comment
|
7.1% regression in rasterize_and_record_micro.top_25 at 495794:495808 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969912350127601104
,
Aug 29 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Nico Weber Commit : 7cd2f6bd73c6a9c6200704e995b18ebb3168ead6 Date : Sat Aug 19 04:23:54 2017 Subject: win: Turn off clang-by-default again for now. Bisect Details Configuration: winx64intel_perf_bisect Benchmark : rasterize_and_record_micro.top_25 Metric : record_time/Wikipedia (1 tab) Change : 8.51% | 0.125333333333 -> 0.136 Revision Result N chromium@495793 0.125333 +- 0.0011547 6 good chromium@495801 0.125333 +- 0.0011547 6 good chromium@495802 0.136833 +- 0.000912871 6 bad <-- chromium@495803 0.136333 +- 0.0011547 6 bad chromium@495805 0.137333 +- 0.0011547 6 bad chromium@495808 0.136 +- 0.0 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=Wikipedia..1.tab. rasterize_and_record_micro.top_25 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969912350127601104 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 29 2017