Issue metadata
Sign in to add a comment
|
14.4%-14.6% regression in angle_perftests at 515817:515837 |
||||||||||||||||||||||
Issue descriptionSee the link to graphs below.
,
Nov 12 2017
Started bisect job https://chromeperf.appspot.com/buildbucket_job_status/8963126929107692464
,
Nov 12 2017
,
Nov 12 2017
=== Auto-CCing suspected CL author cwallez@chromium.org === Hi cwallez@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 : Corentin Wallez Commit : 336129f66f63938212ca0f7069d1a5e483f02042 Date : Fri Nov 10 23:18:12 2017 Subject: Use a packed enum for buffer targets. Bisect Details Configuration: winx64nvidia_perf_bisect Benchmark : angle_perftests Metric : Bindings_d3d11_100_objects_allocated_at_initialization/score Change : 14.72% | 2465.83333333 -> 2102.83333333 Revision Result N chromium@515816 2465.83 +- 18.1888 6 good chromium@515818 2442.67 +- 112.193 6 good chromium@515818,angle@336129f66f 2085.33 +- 37.3006 6 bad <-- chromium@515819 2086.67 +- 26.5957 6 bad chromium@515822 2079.33 +- 16.5932 6 bad chromium@515827 2095.0 +- 42.5441 6 bad chromium@515837 2102.83 +- 37.747 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/8963126929107692464 For feedback, file a bug with component Speed>Bisection
,
Dec 7 2017
This has been mostly fixed with a tiny regression still remaining.
,
Dec 7 2017
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by 42576172...@developer.gserviceaccount.com
, Nov 12 2017