Issue metadata
Sign in to add a comment
|
5%-5.7% regression in image_decoding.image_decoding_measurement at 495788:495808 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 29 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8969912361091010864
,
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: winx64nvidia_perf_bisect Benchmark : image_decoding.image_decoding_measurement Metric : ImageDecoding_avg/ImageDecoding_avg Change : 5.81% | 42.6712083333 -> 45.1497666667 Revision Result N chromium@495801 42.6712 +- 0.287108 6 good chromium@495802 45.2641 +- 0.502347 6 bad <-- chromium@495803 45.1864 +- 0.277693 6 bad chromium@495805 45.2487 +- 0.28212 6 bad chromium@495808 45.1498 +- 0.646969 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 image_decoding.image_decoding_measurement More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8969912361091010864 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