Issue metadata
Sign in to add a comment
|
9%-9.6% regression in angle_perftests at 510800:510886 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Oct 25 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8964802057044219552
,
Oct 25 2017
Suspecting "win: Re-enable Clang by default" No ANGLE rolls in regression range.
,
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: winx64nvidia_perf_bisect Benchmark : angle_perftests Metric : Bindings_gl_100_objects_allocated_at_initialization/score Change : 5.25% | 2584.11111111 -> 2448.33333333 Revision Result N chromium@510799 2584.11 +- 168.08 9 good chromium@510821 2625.67 +- 120.139 6 good chromium@510823 2641.67 +- 95.0649 6 good chromium@510824 2436.17 +- 48.3201 6 bad <-- chromium@510827 2446.0 +- 22.891 6 bad chromium@510832 2434.0 +- 67.0522 6 bad chromium@510843 2433.33 +- 73.8738 6 bad chromium@510886 2448.33 +- 22.701 6 bad To Run This Test .\src\out\Release_x64\angle_perftests.exe --test-launcher-print-test-stdio=always --test-launcher-jobs=1 More information on addressing performance regressions: http://g.co/ChromePerformanceRegressions Debug information about this bisect: https://chromeperf.appspot.com/buildbucket_job_status/8964802057044219552 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