Issue metadata
Sign in to add a comment
|
18.9% regression in media_perftests at 485087:485139 |
||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Jul 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974425533695018416
,
Jul 10 2017
=== BISECT JOB RESULTS === Bisect failed for unknown reasons Please contact the team (see below) and report the error. Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : media_perftests Metric : audio_converter/convert_pass_through To Run This Test .\src\out\Release_x64\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/8974425533695018416 For feedback, file a bug with component Speed>Bisection
,
Jul 10 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974415865602521312
,
Jul 11 2017
=== Auto-CCing suspected CL author holte@chromium.org === Hi holte@chromium.org, the bisect results pointed to your CL, please take a look at the results. === BISECT JOB RESULTS === Perf regression found with culprit Suspected Commit Author : holte Commit : 094e496b0751a1efa5463cba8662318499d1fec8 Date : Fri Jul 07 23:13:48 2017 Subject: Disable UKM on Android Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : media_perftests Metric : audio_converter/convert_pass_through Change : 0.35% | 2054635.96554 -> 2061903.16744 Revision Result N chromium@485086 2054636 +- 46604.4 21 good chromium@485087 2056725 +- 43347.9 14 good chromium@485088 2071476 +- 26633.9 14 bad <-- chromium@485090 2083369 +- 17602.2 6 bad chromium@485093 2075091 +- 20126.3 6 bad chromium@485100 2073614 +- 27520.8 6 bad chromium@485113 2086288 +- 19794.9 6 bad chromium@485139 2061903 +- 36112.5 21 bad To Run This Test .\src\out\Release_x64\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/8974415865602521312 For feedback, file a bug with component Speed>Bisection
,
Jul 11 2017
That CL is an implausible culprit, it has no behavior change on windows.
,
Jul 11 2017
,
Jul 11 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8974405928465133056
,
Jul 11 2017
=== BISECT JOB RESULTS === NO Perf regression found Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : media_perftests Metric : audio_converter/convert_pass_through Revision Result N chromium@484978 2068192 +- 118770 21 good chromium@485148 2062111 +- 81745.9 21 bad To Run This Test .\src\out\Release_x64\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/8974405928465133056 For feedback, file a bug with component Speed>Bisection
,
Jul 11 2017
,
Jul 11 2017
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Jul 10 2017