Issue metadata
Sign in to add a comment
|
2.6%-122.2% regression in media_perftests at 510769:510909 |
||||||||||||||||||||||
Issue descriptionLooks like some things improved and some things regressed. Caleb was here.
,
Oct 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964742315445565056
,
Oct 25 2017
=== BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : Hans Wennborg Commit : 22525134c75ca2a005997a717f6887a23af86210 Date : Mon Oct 23 17:10:25 2017 Subject: win: Re-enable Clang by default Bisect Details Configuration: win_8_perf_bisect Benchmark : media_perftests Metric : clockless_playback/sfx_u8.wav Change : 97.77% | 5376.73833071 -> 10633.5191966 Revision Result N chromium@510776 5376.74 +- 800.554 6 good chromium@510813 4886.55 +- 490.728 6 good chromium@510822 5213.34 +- 564.691 6 good chromium@510823 5568.83 +- 1103.06 6 good chromium@510824 10655.6 +- 3352.86 6 bad <-- chromium@510825 9253.64 +- 1940.2 6 bad chromium@510827 10817.2 +- 1497.71 6 bad chromium@510831 10088.7 +- 1770.63 6 bad chromium@510849 10633.5 +- 2689.52 6 bad To Run This Test .\src\out\Release\media_perftests.exe --single-process-tests More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964742315445565056 For feedback, file a bug with component Speed>Bisection |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Oct 25 2017