Issue metadata
Sign in to add a comment
|
5.3% regression in image_decoding.image_decoding_measurement at 495794:495808 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Aug 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8970287395139301056
,
Aug 25 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 : image_decoding.image_decoding_measurement Metric : ImageDecoding_avg/ImageDecoding_avg Change : 4.53% | 43.35655 -> 45.3194583333 Revision Result N chromium@495793 43.3566 +- 0.0830135 6 good chromium@495801 43.1664 +- 0.862437 6 good chromium@495802 45.535 +- 0.109482 6 bad <-- chromium@495803 45.2977 +- 0.131316 6 bad chromium@495805 45.5346 +- 0.141883 6 bad chromium@495808 45.3195 +- 0.105636 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/8970287395139301056 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Aug 25 2017