«13

Comments

  • RayDAntRayDAnt Posts: 360
    edited September 12

    1. Summarized Benchmark Results

     

    notes:

    • All performance tables currently updated as of this post
    • Please post ONLY benchmark results and discussion of them in this thread
    • For in-depth discussion of issues pertaining to benchmarking in general go here
    • All MSRP values sourced from techpowerup.com's CPU and GPU databases
    • Starred ( * ) MSRP values approximate due to CPU/GPU model having passed out of active production

     

     

    1.1 Iray RTX 2019.1.3

    Found in the following Daz Studio Release(s):

    • Daz Studio 4.12.0.073 Beta
    • Daz Studio 4.12.0.067 Beta
    • Daz Studio 4.12.0.060 Beta
    • Daz Studio 4.12.0.047 Beta
    • Daz Studio 4.12.0.042 Beta

    Active Rendering Devices

    GPU/CPU Models

    Scene Capacity

    (Gigabytes)

    Render Speed

    (iterations per second)

    MSRP

    (USD)

    Overall Value

    (iterations per hour/MSRP)

    Titan RTX 24 08.021 $2499.00 11.555
    Titan RTX + i7-8700K 24 07.311    
    Titan V + Titan V + Titan Xp + Titan Xp 12 23.662    
    Titan V + Titan V 12 15.709    
    Titan V 12 08.047 $2999.00 09.660
    Titan Xp 12 04.496 $1199.00 13.499
    RTX 2080Ti + RTX 2080Ti 11 14.554    
    GTX 1050 2GB 02 00.769 $109.00 25.398
    i7-8700K   00.480 $349.99 04.937

     

    1.2 Iray RTX 2019.1.1

    Found in the following Daz Studio Release(s):

    • Daz Studio 4.12.0.033 Beta

    Active Rendering Devices

    GPU/CPU Models

    Scene Capacity 

    (Gigabytes)

    Render Speed

    (iterations per second)

    MSRP

    (USD)

    Overall Value

    (iterations per hour/MSRP)

    Titan RTX 24 07.772 $2499.00 11.196
    Titan RTX + i7-8700K 24 07.481    
    RTX 2080Ti + RTX 2080Ti 11 13.315    
    RTX 2080Ti + GTX 1080Ti 11 10.726    
    GTX 1080Ti + GTX 1080Ti 11 07.719    
    RTX 2080Ti 11 06.991 $999.00 25.193
    GTX 1080Ti 11 03.934 $699.00* 20.261
    RTX 2080 + GTX 1070 08 07.925    
    RTX 2080 08 05.750 $699.00* 29.614
    GTX 1070 + GTX 1070 08 04.895    
    GTX 1070Ti 08 02.777 $399.00* 25.056
    GTX 1070 08 02.626 $379.00* 24.944
    GTX 1080Ti + GTX 980Ti 06 06.392    
    GTX 980Ti 06 02.587 $549.00* 16.964
    GTX 1070 + GTX 960 04 03.566    
    GTX 1070 + GTX 960 + Ryzen 5 2600X 04 03.549    
    GTX 960 04 01.043 $199.00* 18.868
    Ryzen 5 2600X   00.486 $149.99 11.665
    i7-8700K   00.481 $349.99 04.948

     

     

    1.3 Iray 2018.1.3

    Found in the following Daz Studio Release(s):

    • Daz Studio 4.11.0.383
    • Daz Studio 4.11.0.383 Beta

    Active Rendering Devices

    GPU/CPU Models

    Scene Capacity

    (Gigabytes)

    Render Speed

    (iterations per second)

    MSRP

    (USD)

    Overall Value

    (iterations per hour/MSRP)

    Titan RTX 24 07.197 $2499.00 10.368
    Titan RTX + i7-8700K 24 06.956    
    Titan V + Titan V + Titan Xp + Titan Xp 12 22.329    
    Titan V + Titan V 12 15.227    
    Titan V 12 07.776 $2999.00 09.334
    Titan Xp 12 03.992 $1199.00 11.986
    RTX 2080Ti + RTX 2080Ti 11 11.892    
    RTX 2080Ti + GTX 1080Ti 11 09.519    
    RTX 2080Ti 11 06.195 $999.00 23.325
    GTX 1080Ti 11 03.381 $699.00* 17.413
    RTX 2080 + GTX 1070 08 07.056    
    RTX 2080 08 05.230 $699.00* 26.936
    GTX 1080 + GTX 1080 + Ryzen 7 3700X 08 04.913    
    GTX 1080 + GTX 1080 08 04.519    
    RTX 2070 08 03.650 $499.00 26.333
    GTX 1080 08 02.342 $599.00* 14.075
    GTX 1070Ti 08 02.337 $399.00* 21.086
    GTX 1070 08 01.961 $379.00* 18.627
    GTX 1080Ti + GTX 980Ti 06 05.362    
    GTX 980Ti 06 02.094 $649.00* 11.615
    GTX 1050 2GB 02 00.621 $109.00 20.510
    i9-7980XE   01.010 $1999.00 01.819
    Ryzen 7 3700X   00.633 $329.99 6.906
    i7-8700K   00.414 $349.99 04.258

     

     

    1.4 Iray 2017.0.1

    Found in the following Daz Studio Release(s):

    • Daz Studio 4.10.0.123

    Active Rendering Devices

    GPU/CPU Models

    Scene Capacity

    (Gigabytes)

    Render Speed

    (iterations per second)

    MSRP

    (USD)

    Overall Value

    (iterations per hour/MSRP)

    Titan Xp + Titan Xp + Titan X (Pascal) 12 13.569    
    GTX 1080Ti + GTX 1080Ti 11 07.508    

     

    Post edited by RayDAnt on
  • RayDAntRayDAnt Posts: 360
    edited September 4

    2. Benchmark Results

     

    2.1 Nvidia GPUs

    Titan RTX:

    Contributor     OS           Driver          DS Version              OptiX     Total Rendering Time        Device Render     Iteration Rate     Loading Time
    RayDAnt         W10 1903     436.15 TCC      4.12.0.067 Beta x64     On*       3 minutes 49.18 seconds     224.405           8.021              4.775
    RayDAnt         W10 1903     436.02 TCC      4.12.0.060 Beta x64     On*       3 minutes 49.40 seconds     224.474           8.019              4.926
    RayDAnt         W10 1903     431.60 TCC      4.12.0.042 Beta x64     On*       3 minutes 56.96 seconds     230.966           7.793              5.994
    RayDAnt         W10 1903     436.15 WDDM     4.12.0.067 Beta x64     On*       3 minutes 57.44 seconds     232.527           7.741              4.913
    RayDAnt         W10 1903     436.02 WDDM     4.12.0.060 Beta x64     On*       4 minutes 10.14 seconds     245.123           7.343              5.017
    RayDAnt         W10 1903     431.60 WDDM     4.12.0.042 Beta x64     On*       4 minutes 18.82 seconds     253.092           7.112              5.728
    
    RayDAnt         W10 1903     431.60 TCC      4.12.0.033 Beta x64     On*       3 minutes 56.45 seconds     231.590           7.772              4.860
    RayDAnt         W10 1903     431.36 WDDM     4.12.0.033 Beta x64     On*       4 minutes 4.9 seconds       239.117           7.528              5.783
    
    RayDAnt         W10 1903     436.15 TCC      4.11.0.383 x64          On        4 minutes 14.97 seconds     250.111           7.197              4.859
    RayDAnt         W10 1903     431.36 TCC      4.11.0.383 x64          On        4 minutes 15.93 seconds     251.184           7.166              4.746
    RayDAnt         W10 1903     436.15 WDDM     4.11.0.383 x64          On        4 minutes 24.19 seconds     258.950           6.951              5.240
    RayDAnt         W10 1903     431.36 WDDM     4.11.0.383 x64          On        4 minutes 27.50 seconds     262.665           6.853              4.835
    RayDAnt         W10 1903     436.15 TCC      4.11.0.383 x64          Off       4 minutes 33.50 seconds     268.127           6.713              5.373
    RayDAnt         W10 1903     431.36 TCC      4.11.0.383 x64          Off       4 minutes 35.57 seconds     270.057           6.665              5.513
    RayDAnt         W10 1903     436.15 WDDM     4.11.0.383 x64          Off       4 minutes 41.93 seconds     276.304           6.515              5.626
    RayDAnt         W10 1903     431.36 WDDM     4.11.0.383 x64          Off       4 minutes 56.36 seconds     290.852           6.189              5.508
    

     

    Titan V:

    Contributor     OS           Driver          DS Version              OptiX     Total Rendering Time        Device Render     Iteration Rate     Loading Time
    JD_Mortal       W10 1903     436.15 TCC      4.12.0.067 Beta x64     On        3 minutes 48.31 seconds     223.698           8.047              4.612
    JD_Mortal       W10 1903     436.15 WDDM     4.12.0.067 Beta x64     On        3 minutes 58.91 seconds     234.216           7.685              4.694
    
    JD_Mortal       W10 1903     436.15 TCC      4.11.0.383 x64          On        3 minutes 55.66 seconds     231.485           7.776              4.295
    JD_Mortal       W10 1903     436.15 WDDM     4.11.0.383 x64          On        4 minutes 5.98 seconds      241.685           7.448              4.295
    JD_Mortal       W10 1903     436.15 TCC      4.11.0.383 x64          Off       4 minutes 16.18 seconds     250.779           7.178              5.401
    JD_Mortal       W10 1903     436.15 WDDM     4.11.0.383 x64          Off       4 minutes 27.20 seconds     261.474           6.884              5.726
    

     

    RTX 2080Ti:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time        Device Render     Iteration Rate     Loading Time
    Dim Reaper      W10 1803     431.60     4.12.0.033 Beta x64     Off*      4 minutes 25.3 seconds      257.470           6.991              7.830
    allinn1000      W10 1903     430.86     4.12.0.033 Beta x64     On*       4 minutes 30.29 seconds     265.272           6.785              5.018
    
    Dim Reaper      W10 1803     430.64     4.11.0.383 x64          On        4 minutes 58.20 seconds     290.554           6.195              7.646
    

     

    RTX 2080:

    Contributor       OS          Driver     DS Version              OptiX     Total Rendering Time        Device Render     Iteration Rate     Loading Time
    A Paper Tiger     W8 9600     430.86     4.12.0.033 Beta x64     On*       5 minutes 20.48 seconds     313.011           5.750              7.469
    
    A Paper Tiger     W8 9600     430.86     4.11.0.383 x64          On        5 minutes 51.33 seconds     344.199           5.230              7.131
    

     

    RTX 2070:

    Contributor     OS           Driver     DS Version         OptiX     Total Rendering Time        Device Render     Iteration Rate     Loading Time
    Drip            W10 1903     430.86     4.11.0.383 x64     Off       8 minutes 23.21 seconds     493.208           3.650              10.000
    Drip            W10 1903     430.86     4.11.0.383 x64     On        8 minutes 37.38 seconds     507.814           3.545              9.566
    

     

    Titan Xp:

    Contributor     OS           Driver          DS Version              OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    JD_Mortal       W10 1903     426.15 TCC      4.12.0.067 Beta x64     On*       6 minutes 45.83 seconds      400.361           4.496              5.469
    JD_Mortal       W10 1903     426.15 WDDM     4.12.0.067 Beta x64     On*       6 minutes 55.35 seconds      409.981           4.390              5.369
    
    JD_Mortal       W10 1903     426.15 TCC      4.11.0.383 x64          On        7 minutes 35.27 seconds      450.900           3.992              4.370
    JD_Mortal       W10 1903     426.15 WDDM     4.11.0.383 x64          On        8 minutes 7.50 seconds       482.323           3.732              5.177
    JD_Mortal       W10 1903     426.15 TCC      4.11.0.383 x64          Off       8 minutes 24.48 seconds      499.044           3.607              5.436
    JD_Mortal       W10 1903     426.15 WDDM     4.11.0.383 x64          Off       8 minutes 40.59 seconds      514.893           3.496              5.697
    

     

    GTX 1080Ti:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    Dim Reaper      W10 1803     430.64     4.12.0.033 Beta x64     On*       7 minutes 45.3 seconds       457.279           3.936              8.021
    talidesade      W10 1809     431.36     4.12.0.033 Beta x64     Off*      7 minutes 47.61 seconds      457.867           3.931              9.743
    
    Dim Reaper      W10 1803     430.64     4.11.0.383 x64          On        8 minutes 59.70 seconds      532.429           3.381              7.271
    

     

    GTX 1080:

    Contributor     OS           Driver     DS Version       OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    mumia76         W10 1903     431.70     11.0.383 x64     On        13 minutes 4.18 seconds      779.848           2.308              4.332
    mumia76         W10 1903     431.70     11.0.383 x64     On        12 minutes 42.16 seconds     757.945           2.375              4.215
    Iteration Rate AVG = 2.342
    

     

    GTX 1070Ti:

    Contributor       OS           Driver     DS Version              OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    A Paper Tiger     W10 1903     430.86     4.12.0.033 x64          On*       10 minutes 58.40 seconds     648.264           2.777              10.136
    
    A Paper Tiger     W10 1903     430.86     4.11.0.383 x64          On        13 minutes 0.20 seconds      770.149           2.337              10.051
    

     

    GTX 1070:

    Contributor       OS          Driver     DS Version              OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    TheKD             W7 7601     431.36     4.12.0.033 Beta x64     Off*      11 minutes 33.74 seconds     685.427           2.626              8.383
    TheKD             W7 7601     431.36     4.12.0.033 Beta x64     On*       11 minutes 32.81 seconds     686.323           2.623              6.487
    A Paper Tiger     W8 9600     430.86     4.12.0.033 Beta x64     On*       12 minutes 49.99 seconds     762.203           2.362              7.787
    
    A Paper Tiger     W8 9600     430.86     4.11.0.383 x64          On        15 minutes 25.59 seconds     917.842           1.961              7.748
    

     

    GTX 1050 2GB:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    RayDAnt         W10 1903     431.60     4.12.0.042 Beta x64     Off*      39 minutes 9.32 seconds      2340.262          0.769              9.058
    RayDAnt         W10 1903     431.60     4.12.0.042 Beta x64     On*       39 minutes 13.58 seconds     2345.589          0.767              7.991
    
    RayDAnt         W10 1903     431.60     4.11.0.383 x64          On        48 minutes 25.40 seconds     2897.136          0.621              8.264
    RayDAnt         W10 1903     431.60     4.11.0.383 x64          Off       55 minutes 49.78 seconds     3340.848          0.539              8.932
    

     

    GTX 980Ti:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    Dim Reaper      W10 1803     430.64     4.12.0.033 Beta x64     On*       11 minutes 43.96 seconds     695.982           2.587              7.978
    
    Dim Reaper      W10 1803     430.64     4.11.0.383 x64          On        14 minutes 26.48 seconds     859.525           2.094              6.955
    

     

    GTX 960:

    Contributor     OS          Driver     DS Version              OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    TheKD           W7 7601     431.36     4.12.0.033 Beta x64     On*       28 minutes 53.53 seconds     1725.972          1.043              7.558
    
    Post edited by RayDAnt on
  • RayDAntRayDAnt Posts: 360
    edited September 3

    2.2 Intel CPUs

    i9-7980XE:

    Contributor     OS           DS Version         OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    JD_Mortal       W10 1903     4.11.0.383 x64     On        29 minutes 52.70 seconds     1782.909          1.010              9.791
    JD_Mortal       W10 1903     4.11.0.383 x64     Off       30 minutes 19.50 seconds     1812.990          0.993              6.510
    

     

    i7-8700K:

    Contributor     OS           DS Version              OptiX     Total Rendering Time                 Device Render     Iteration Rate     Loading Time
    RayDAnt         W10 1903     4.12.0.042 Beta x64     On*       1 hours 2 minutes 34.70 seconds      3750.235          0.480              4.465
    
    RayDAnt         W10 1903     4.12.0.033 Beta x64     On*       1 hours 2 minutes 25.52 seconds      3740.472          0.481              5.048
    
    RayDAnt         W10 1903     4.11.0.383 x64          On        1 hours 12 minutes 40.67 seconds     4352.048          0.414              8.622
    RayDAnt         W10 1903     4.11.0.383 x64          Off       1 hours 14 minutes 0.55 seconds      4434.854          0.406              5.696
    

     

     

    2.3 AMD CPUs

    Ryzen 7 3700X:

    Contributor     OS           DS Version         OptiX     Total Rendering Time         Device Render     Iteration Rate     Loading Time
    mumia76         W10 1903     4.11.0.383 x64     On        47 minutes 30.19 seconds     2841.804          0.633              8.386
    

     

    Ryzen 5 2600X:

    Contributor     OS           DS Version              OptiX       Total Rendering Time                Device Render     Iteration Rate     Loading Time
    TheKD           W7 7601      4.12.0.033 Beta x64     On*         1 hours 1 minutes 53.71 seconds     3706.529          0.486              7.181

     

     

    2.4 GPU/CPU Combinations

    Titan RTX + i7-8700K:

    Contributor     OS           Driver          DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    RayDAnt         W10 1903     431.36 WDDM     4.12.0.042 Beta x64     On*       4 minutes 11.79 seconds     246.195               7.311              5.595
    
    RayDAnt         W10 1903     431.36 TCC      4.12.0.033 Beta x64     On*       4 minutes 5.52 seconds      239.909               7.481              4.897
    RayDAnt         W10 1903     431.36 WDDM     4.12.0.033 Beta x64     On*       4 minutes 17.10 seconds     252.273               7.135              4.827
    
    RayDAnt         W10 1903     431.36 TCC      4.11.0.383 x64          On        4 minutes 23.24 seconds     257.724               6.956              4.460
    RayDAnt         W10 1903     431.36 WDDM     4.11.0.383 x64          On        4 minutes 44.23 seconds     279.586               6.438              4.644
    RayDAnt         W10 1903     431.36 TCC      4.11.0.383 x64          Off       4 minutes 40.62 seconds     274.001               6.541              5.419
    RayDAnt         W10 1903     431.36 WDDM     4.11.0.383 x64          Off       4 minutes 56.52 seconds     290.508               6.196              6.012
    

     

    Titan V + Titan V + Titan Xp + Titan Xp:

    Contributor     OS           Driver          DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    JD_Mortal       W10 1903     436.15 TCC^     4.12.0.067 Beta x64     On        1 minutes 22.75 seconds     76.070                23.662             6.680
    JD_Mortal       W10 1903     436.15 WDDM     4.12.0.067 Beta x64     On        1 minutes 25.76 seconds     79.914                22.524             5.846
    
    JD_Mortal       W10 1903     436.15 TCC^     4.11.0.383 x64          On        1 minutes 22.66 seconds     80.613                22.329             2.047
    JD_Mortal       W10 1903     436.15 WDDM     4.11.0.383 x64          On        1 minutes 28.83 seconds     83.698                21.506             5.132
    JD_Mortal       W10 1903     436.15 TCC^     4.11.0.383 x64          Off       1 minutes 32.65 seconds     86.990                20.692             5.660
    JD_Mortal       W10 1903     436.15 WDDM     4.11.0.383 x64          Off       1 minutes 36.72 seconds     90.425                19.906             6.295
    
    ^ one Titan Xp kept in WDDM mode for display functionality

     

    Titan V + Titan V:

    Contributor     OS           Driver         DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    JD_Mortal       W10 1903     436.15 TCC     4.12.0.067 Beta x64     On*       1 minutes 59.20 seconds     114.587               15.709             4.613
    
    JD_Mortal       W10 1903     436.15 TCC     4.11.0.383 x64          On        2 minutes 2.63 seconds      118.214               15.227             4.416
    

     

    RTX 2080Ti + RTX 2080Ti:

    Contributor      OS            Driver         DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    AelfinMaegik     W10 1903      431.60         4.12.0.042 Beta x64     Off*      2 minutes 12.65 seconds     123.675               14.554             8.975
    AelfinMaegik     W10 1903      431.60         4.12.0.042 Beta x64     On*       2 minutes 18.77 seconds     129.627               13.881             9.100
    
    Aala             W10 1903      431.60         4.12.0.033 Beta x64     Off*      2 minutes 17.11 seconds     135.201               13.315             1.909
    AelfinMaegik     W10 1903      431.60 SLI     4.12.0.033 Beta x64     On*       2 minutes 24.16 seconds     135.982               13.237             8.178
    Aala             W10 1903      431.60         4.12.0.033 Brta x64     On*       2 minutes 22.0 seconds      139.184               12.933             2.816
    AelfinMaegik     W10 17134     431.36 SLI     4.12.0.033 Beta x64     On*       2 minutes 25.72 seconds     136.656               13.172             9.064
    
    AelfinMaegik     W10 17134     431.36 SLI     4.11.0.383 x64          On        2 minutes 40.97 seconds     151.359               11.892             9.611
    

     

    RTX 2080Ti + GTX 1080Ti:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    Dim Reaper      W10 1803     431.60     4.12.0.033 Beta x64     Off*      2 minutes 58.70 seconds     167.820               10.726             10.880
    
    Dim Reaper      W10 1803     431.60     4.11.0.383 x64          On*       3 minutes 17.30 seconds     189.098               9.519              8.201
    

     

    RTX 2080 + GTX 1070:

    Contributor       OS          Driver     DS Version             OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    A Paper Tiger     W8 9600     430.86     4.12.0.033 Beta x64     On*       3 minutes 54.87 seconds     227.118               7.925              7.752
    
    A Paper Tiger     W8 9600     430.86     4.11.0.383 x64          On        4 minutes 22.59 seconds     255.111               7.056              7.479
    

     

    Titan Xp + Titan Xp + Titan X (Pascal):

    Contributor     OS           Driver     DS Version         OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    garyh.pub       W10 1809     416.34     4.10.0.123 x64     On        2 minutes 29.56 seconds     132.657               13.569             16.903
    

     

    GTX 1080Ti + GTX 1080Ti:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time       Max Device Render     Iteration Rate     Loading Time
    outrider42      W10 1809     431.36     4.12.0.033 Beta x64     Off*      4 minutes 2.32 seconds     233.194               7.719              9.126
    Aala            W10 1903     431.60     4.12.0.033 Beta x64     Off*      4 minutes 12.51 seconds    250.513               7.185              1.997
    outrider42      W10 1809     431.36     4.12.0.033 Beta x64     On*       4 minutes 1.76 seconds     ?                     ?                  ?
    Aala            W10 1903     431.60     4.12.0.033 Beta x64     On*       4 minutes 12.83 seconds    250.252               7.192              2.578
    
    Aala            W10 1903     431.60     4.10.0.123 x64          On        4 minutes 2.48 seconds     239.733               7.508              2.747
    Aala            W10 1903     431.60     4.10.0.123 x64          Off       4 minutes 27.64 seconds    265.072               6.791              2.568
    

     

    GTX 1080Ti + GTX 980Ti:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    Dim Reaper      W10 1803     431.36     4.12.0.033 Beta x64     On*       4 minutes 49.52 seconds     281.616               6.392              7.904
    
    Dim Reaper      W10 1803     431.36     4.11.0.383 x64          On        5 minutes 43.5 seconds      335.669               5.362              7.831
    

     

    GTX 1080 + GTX 1080 + Ryzen 7 3700X:

    Contributor     OS           Driver     DS Version         OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    mumia76         W10 1903     431.70     4.11.0.383 x64     On        6 minutes 10.75 seconds     366.407               4.913              4.913
    

     

    GTX 1080 + GTX 1080:

    Contributor     OS           Driver     DS Version         OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    mumia76         W10 1903     431.70     4.11.0.383 x64     On        6 minutes 42.84 seconds     398.312               4.519              4.528
    

     

    GTX 1070 + GTX 1070:

    Contributor     OS           Driver     DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    LCJD            W10 1903     431.36     4.12.0.033 Beta x64     Off*      6 minutes 14.55 seconds     367.699               4.895              6.851
    

     

    GTX 1070 + GTX 960 + Ryzen 5 2600X:

    Contributor     OS          Driver     DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    TheKD           W7 7601     431.61     4.12.0.033 Beta x64     On*       9 minutes 12.87 seconds     546.102               3.256              6.768
    TheKD           W7 7601     431.61     4.12.0.033 Beta x64     Off*      8 minutes 27.25 seconds     499.952               3.549              7.298
    

     

    GTX 1070 + GTX 960:

    Contributor     OS          Driver     DS Version              OptiX     Total Rendering Time        Max Device Render     Iteration Rate     Loading Time
    TheKD           W7 7601     431.36     4.12.0.033 beta x64     Off*      8 minutes 32.89 seconds     504.705               3.566              8.185
    TheKD           W7 7601     431.36     4.12.0.033 beta x64     On*       8 minutes 32.69 seconds     505.825               3.559              6.865
    

     

    * Function of OptiX Prime acceleration checkbox uncertain due to changes in raytracing handling by low-level APIs.

    Post edited by RayDAnt on
  • RayDAntRayDAnt Posts: 360
    edited September 3

    3. Contributing Your Own Results To This Thread:

     

    3.1 Before You Begin

     

    Make sure the following Daz Studio settings are set to their defaults:

    • Edit [menu> Preferences > Scene > Backdrop Color: > Ignore when opening a Scene file = Unchecked (default)
    • Edit [menu> Preferences > Scene > Backdrop Image: > Ignore when opening a Scene file = Unchecked (default)
    • Edit [menu> Preferences > Scene > Render Settings: > Ignore when opening a Scene file = Unchecked (default)
    • Edit [menu> Preferences > Interface > Miscellaneous > Multi-Threading = On (default)
    • Render Settings [pane> Editor [tab> Optimization > Instancing Optimization = Speed/Auto (default)
    • Draw Settings [paneDrawStyle = Texture Shaded (default)

     

    3.2 Running The Benchmark

     

    Step 1: Close all running programs (including any open instances of Daz Studio) before continuing (failing to do so may artificially decrease your measured rendering performance.)
    Step 2: Download this benchmarking scene and open it in Daz Studio.
    Step 3: Go to Render Settings [pane> Advanced > Hardware > Photoreal Devices and select only the device(s) you currently wish to test.
    Step 4: In the same settings window make sure to select/deselect OptiX Prime Acceleration depending on your preference for this specific test run.
    Step 5: Press Render and wait until the scene fully finishes rendering.
    Step 6: OPTIONAL Save (with a unique file name) the final rendered image for later reference.
    Step 7: Close Daz Studio completely before continuing (failing to do so may make it impossible for you to fully report your benchmarking results.)

     

    3.3 Reporting Your Results

     

    Step 1: Start a new post in this thread and paste the following template into it:

    System Configuration
    System/Motherboard: BRAND MODEL
    CPU: BRAND MODEL @ SPEED/stock (if left at defaults)
    GPU: BRAND MODEL @ SPEED/stock (if left at defaults)
    System Memory: BRAND MODEL CAPACITY TYPE @ SPEED
    OS Drive: BRAND MODEL CAPACITY
    Asset Drive: BRAND MODEL CAPACITY/Same (if same as OS)
    Operating System: EDITION VERSION BUILD
    Nvidia Drivers Version: VERSION MODE
    Daz Studio Version: VERSION BITS
    Optix Prime Acceleration: STATE

    Benchmark Results
    DAZ_STATS
    IRAY_STATS
    Iteration Rate: (DEVICE_ITERATION_COUNT / DEVICE_RENDER_TIME) iterations per second
    Loading Time: ((TRT_HOURS * 3600 + TRT_MINUTES * 60 + TRT_SECONDS) - DEVICE_RENDER_TIME) seconds

     

    Step 2: Fill in System Configuration with your info. If specific branding information is unavailable for a particular component (eg. unbranded SSDs/RAM sticks in a pre-built system) simply omit it.
     

    Step 3: Navigate to the Daz Studio log file (found in "AppData\Roaming\DAZ 3D\Studio4\log.txt" or "AppData\Roaming\DAZ 3D\Studio4 Public Build\log.txt" for the public beta), scroll to the very end of the file, and look for lines of text resembling the following:

    DAZ_STATS:

    2019-03-15 00:30:37.317 Finished Rendering
    2019-03-15 00:30:37.358 Total Rendering Time: 26 minutes 35.45 seconds
    

    IRAY_STATS:

    2019-03-15 00:32:31.455 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Device statistics:
    2019-03-15 00:32:31.455 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1050): 	 1000 iterations, 6.813s init, 1584.264s render
    

     

    Step 4: Copy these lines and replace DAZ_STATS and IRAY_STATS under Benchmark Results in the template with them. Then take special care in calculating the correct values for Iteration Rate and Loading Time. These two statistics are essential for understanding how your system's rendering performance compares to others' - not Total Rendering Time itself.
    Total Rendering Time, because of the way it is computed by Daz Studio, is an invalid statistic for measuring rendering performance. Especially on systems with high-performance rendering hardware.

    Step 5: OPTIONAL Attach the rendered image from your benchmark run to your post.
     

    Step 6: Submit your post and check back (by seeing which post this note under Table of Contents currently leads to) for it to be incorporated into the Performance Tables at the beginning of this thread (If you really want to help speed the update process along, copy the relevant tables from the beginning of this thread, incorporate your results, and then post the updated tables in the same post as your original benchmark results.)

     


     4. About The Benchmarking Scene Used

     

    4.1 Design Factors

     

    In order to present the most robust benchmarking scene possible, the following key factors were first identified (as part of an extensive study on the relative advantages/pitfalls of a variety of existing DS/Iray benchmarking scenes freely available at the time) and then used as design paramaters for the creation of the scene used to generate all of this thread's relative performance data. These factors are:

    • Content Availability: In order to maintain maximum compatibility across different installations of Daz Studio, scene content must be limited to only that which is freely available to all Daz Studio users (ie. Genesis base figures and accessories, demo scene content, and/or object primitves.)
    • Content Variety: Since the ultimate goal is to study real-world Daz Studio rendering performance, scene element variety should resemble - to as great an extent as minimum memory requirments allow - the same variety of content as typical of scenes created by actual DS users (ie. at least one fully textured/accessorized Genesis figure in a lit enviroment accompanied by one or more object primitives.) 
    • Content Familiarity: As both a direct shout-out to past efforts and a way to stress as many of the exact same rendering performance concerns as possible (eg. the influence of dual lobe specularity skin shading) a decision was made early on to reuse as many individual scene elements from previous freely available benchmarking scenes as possible in the creation of a new scene (particularly the following scenes from Daz Studio users/developers Sickleyieldoutrider42DAZ_Rawb, and Aala.)
    • Memory Requirements: Because having adequate video memory is a hard limit to successful rendering in Daz Studio's implementation of Iray, the amount of content in the scene must be limited to only what will fit within the memory limits of the smallest capacity card on which it is reasonably expected to be run (eg. no more than 2GB, since that is the smallest common capacity found on recent generation low-end cards like the GTX 1050.)
    • Render Stop Condition: By default, Iray simultaneously enforces three different stop conditions by which to judge the "completion" point of a scene. These are: time, convergence ratio, and iteration count. Since the first two of these conditions are less granularly calcualted by Iray than the third - and two or more simultaneous stop conditions can lead to inconsistent render completion behaviors across widely differently performing hardware -  a scene must be configured to to use iteration count and iteration count only as its rendering stop condition in order to exhibit identical rendering behavior across a diverse set of testing hardware platforms.
    • Render Duration: Although most rendering performance statistics reported by Daz Studio appear in the form of time-consistent-sounding figures (eg. total time spent rendering, total iterations rendered, etc.) the reality is that individual iteration render times vary every bit as much as individual frame render times do in mainstream computer gaming. This means that benchmarking runs consisting of fewer iterations/frames are more susceptible to outlier performance events (such as sudden, brief unexpected CPU usage spikes) muddying up overall results. Therefore it is generally best practice to design a benchmark to run for as long as possible in order to get the most useful/accurate results. At the same time, most low-end hardware is incapable of rendering anywhere near the number of iterations most high-end hardware can in  a reasonable amount of time. And rendering the same scene to different iteration counts does not lead to comparable data. Therefore it was determined that a happy medium iteration count (enough to stress high-end hardware but not too many for low-end hardware to handle as well) would be needed.
    • Additional Design Considerations as brought up by JD_Mortal in this post.

     

    4.2 The End Result

     

    >>> RayDAnt_DS_Iray_Benchmark_2019A.duf <<< download here!

     

    Final RenderExpected viewport view

    Iteration Time Graph

    • Content
      • Cornell box interior environment
      • Seven scene object primitives (featuring various surface properties)
      • One light emiting scene object primitive
      • One fully textured Genesis 8 Female (featuring dual-lobe specularity SSS)
      • One G8F hairpiece (native Iray materials)
      • One G8F clothing top (native Iray materials)
      • One G2F clothing bottom (converted for G8F and updated for Iray material use)
    • Memory Requirements: ~1430MB VRAM (as reported by GPU-Z)
    • Render Stop Condition: Iterations only (all other conditions actively disabled)
    • Render Duration: 1800 iterations
      • Approximate Render Time (GTX 1050 2GB): 50 minutes
      • Approximate Render Time (Titan RTX): 4 minutes

     


    5. Tips & Tricks

     

    5.1 Submitting multiple benchmark results at the same time

     

    If you want to contribute multiple sets of results from the same computer at the same time (eg. two back-to-back runs illustrating the performance difference between OptiX Prime On and OptiX Prime Off) format your post like this:

    System Configuration
    System/Motherboard: BRAND MODEL
    CPU: BRAND MODEL @ SPEED/stock (if left at defaults)
    GPU: BRAND MODEL @ SPEED/stock (if left at defaults)
    System Memory: BRAND MODEL CAPACITY TYPE @ SPEED
    OS Drive: BRAND MODEL CAPACITY
    Asset Drive: BRAND MODEL CAPACITY/Same (if same as OS Drive)
    Operating System: EDITION VERSION BUILD
    Nvidia Drivers Version: VERSION MODE
    Daz Studio Version: VERSION BITS

    Benchmark Results
    Optix Prime Acceleration: On
    DAZ_STATS
    IRAY_STATS
    Iteration Rate: (DEVICE_ITERATION_COUNT / DEVICE_RENDER_TIME) iterations per second
    Preload Time: ((TRT_HOURS * 3600 + TRT_MINUTES * 60 + TRT_SECONDS) - DEVICE_RENDER_TIME) seconds

    Optix Prime Acceleration: Off
    DAZ_STATS
    IRAY_STATS
    Iteration Rate: (DEVICE_ITERATION_COUNT / DEVICE_RENDER_TIME) iterations per second
    Loading Time: ((TRT_HOURS * 3600 + TRT_MINUTES * 60 + TRT_SECONDS) - DEVICE_RENDER_TIME) seconds

     

     

    5.2 Submitting benchmark results for multi-GPU and/or CPU combinations 

     

    Use the following template when submitting results for CPU + GPU rendering or GPU1 + GPU2 + etc... in multi-GPU systems:

    System Configuration
    System/Motherboard: BRAND MODEL
    CPU: BRAND MODEL @ SPEED/Stock (if left at defaults)
    GPU: GPU1 BRAND MODEL @ SPEED/stock (if left at defaults), GPU2 BRAND MODEL @ SPEED/stock (if left at defaults), ...
    System Memory: BRAND MODEL CAPACITY TYPE @ SPEED
    OS Drive: BRAND MODEL CAPACITY
    Asset Drive: BRAND MODEL CAPACITY/Same (if same as OS)
    Operating System: EDITION VERSION BUILD
    Nvidia Drivers Version: VERSION MODE
    Daz Studio Version: VERSION BITS
    Optix Prime Acceleration: STATE

    Benchmark Results
    DAZ_STATS
    IRAY_STATS
    Rendering Performance: [DEVICE_ITERATION_COUNT(sum of all values) / DEVICE_RENDER_TIME_(largest value)] iterations per second
    Loading Time: [(TRT_HOURS * 3600 + TRT_MINUTES * 60 + TRT_SECONDS) - DEVICE_RENDER_TIME_(largest value)] seconds

     

     


    6. Additional Resources

     

    6.1 Other Daz Studio user-generated benchmarking efforts

     

    6.2 Official Daz Studio development information

    duf
    duf
    RayDAnt_DS_Iray_Benchmark_2019A.duf
    1M
    RayDAnt_DS_Iray_Benchmark_2019A.rendered.png
    900 x 900 - 1M
    RayDAnt_DS_Iray_Benchmark_2019A.viewport.png
    563 x 795 - 30K
    RayDAnt_DS_Iray_Benchmark_2019A.itg.png
    600 x 371 - 20K
    Post edited by RayDAnt on
  • LCJDLCJD Posts: 12
    edited August 3

    (UPDATED) 08/03/19

    System Configuration

    Operating System: Windows 10 64bits Pro version 1903 build
    Nvidia Drivers Version: 431.36 GRD


    System/Motherboard: MSI Z270 SLI Plus
    CPU: Intel i7-6700K @ 4.2 Ghz
    GPU: GTX 1070 x2 @ 1980Mhz
    System Memory: G-Skill 32GB DDR4 @ 2200 Mhz

    Benchmark Results - GTX 1070 x2 Only

    Daz Studio Version: 4.12.0.033 Beta 64-bit
    Optix Prime Acceleration: No
    Total Rendering Time: 6 minutes 14.55 seconds

    CUDA device 1 (GeForce GTX 1070): 881 iterations, 4.438s init, 367.075s render

    CUDA device 0 (GeForce GTX 1070): 919 iterations, 3.736s init, 367.699s render

    Iteration Rate: (1800 / 367.387) = 4.899 iterations per second
    System Overhead: ((0 + 373 + 14.55) - 367.387) = (373.1455 - 367.387) = 5.7585 seconds

    Post edited by LCJD on
  • RayDAntRayDAnt Posts: 360
    edited September 3

    System Configuration
    System/Motherboard: Gigabyte Z370 Aorus Gaming 7
    CPU: Intel i7-8700K @ stock (MCE enabled)
    GPU: Nvidia Titan RTX @ stock (watercooled)
    System Memory: Corsair Vengeance LPX 32GB DDR4 @ 3000Mhz
    OS Drive: Samsung Pro 970 512GB NVME SSD
    Asset Drive: Sandisk Extreme Portable SSD 1TB
    Operating System: Windows 10 Pro version 1903 build 18362.239 
    Nvidia Drivers Version: 431.36 GRD WDDM

     

    Benchmark Results - Titan RTX Only
    Daz Studio Version: 4.12.0.033 Beta 64-bit
    Optix Prime Acceleration: On
    Total Rendering Time: 4 minutes 4.9 seconds
    CUDA device 0 (TITAN RTX): 1800 iterations, 2.355s init, 239.117s render
    Iteration Rate: (1800 / 239.117) = 7.528 iterations per second
    Loading Time: ((0 + 240 + 4.9) - 239.117) = (244.9 - 239.117) = 5.783 seconds

    Benchmark Results - Titan RTX Only
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: On
    Total Rendering Time: 4 minutes 27.50 seconds
    CUDA device 0 (TITAN RTX): 1800 iterations, 2.297s init, 262.665s render
    Iteration Rate: (1800 / 262.665) = 6.853 iterations per second
    Loading Time: ((0 + 240 + 27.50) - 262.665) = (267.50 - 262.665) = 4.835 seconds

    Benchmark Results - Titan RTX Only
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: Off
    Total Rendering Time: 4 minutes 56.36 seconds
    CUDA device 0 (TITAN RTX): 1800 iterations, 3.180s init, 290.852s render
    Iteration Rate: (1800 / 290.852) = 6.189 iterations per second
    Loading Time: ((0 + 240 + 56.36) - 290.852) = (296.36 - 290.852) = 5.508 seconds

     

    Benchmark Results - Intel i7-8700K Only
    Daz Studio Version: 4.12.0.033 64-bit
    Optix Prime Acceleration: On
    Total Rendering Time: 1 hours 2 minutes 25.52 seconds
    CPU: 1800 iterations, 2.358s init, 3740.472s render
    Iteration Rate: (1800 /  3740.472) = 0.481 iterations per second
    Loading Time: ((3600 + 120 + 25.52) - 3740.472) = (3745.52 - 3740.472) = 5.048 seconds

    Benchmark Results - Intel i7-8700K Only
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: On
    Total Rendering Time: 1 hours 12 minutes 40.67 seconds
    CPU: 1800 iterations, 6.147s init, 4352.048s render
    Iteration Rate: (1800 /  4352.048) = 0.414 iterations per second
    Loading Time: ((3600 + 720 + 40.67) - 4352.048) = (4360.67 - 4352.048) = 8.622 seconds

    Benchmark Results - Intel i7-8700K Only
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: Off
    Total Rendering Time: 1 hours 14 minutes 0.55 seconds
    CPU: 1800 iterations, 3.306s init, 4434.854s render
    Iteration Rate: (1800 /  4434.084) = 0.406 iterations per second
    Loading Time: ((3600 + 840 + 0.55) - 4434.854) = (4440.55 - 4434.854) = 5.696 seconds

     

    Benchmark Results - Titan RTX + Intel i7-8700K
    Daz Studio Version: 4.12.0.033 64-bit
    Optix Prime Acceleration: On
    Total Rendering Time: 4 minutes 17.10 seconds
    CUDA device 0 (TITAN RTX): 1691 iterations, 2.390s init, 250.967s render
    CPU: 109 iterations, 2.162s init, 252.273s render
    Iteration Rate: (1800 /  252.273) = 7.135 iterations per second
    Loading Time: ((0 + 240 + 17.10) - 252.273) = (257.10 - 252.273) = 4.827 seconds

    Benchmark Results - Titan RTX + Intel i7-8700K
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: On
    Total Rendering Time: 4 minutes 44.23 seconds
    CUDA device 0 (TITAN RTX): 1696 iterations, 2.388s init, 277.534s render
    CPU: 104 iterations, 2.022s init, 279.586s render
    Iteration Rate: (1800 /  279.586) = 6.438 iterations per second
    Loading Time: ((0 + 240 + 44.23) - 279.586) = (284.23 - 279.586) = 4.644 seconds

    Benchmark Results - Titan RTX + Intel i7-8700K
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: Off
    Total Rendering Time: 4 minutes 56.52 seconds
    CUDA device 0 (TITAN RTX): 1695 iterations, 3.257s init, 290.945s render
    CPU: 105 iterations, 2.969s init, 290.508s render
    Iteration Rate: (1800 /  290.508) = 6.196 iterations per second
    Loading Time: ((0 + 240 + 56.52) - 290.508) = (296.52 - 290.508) = 6.012 seconds


     

    LCJD, can you add the rest of the info (check the post before yours) to your post? Just Total Rendering Time isn't enough to caculate a final result for this benchmark. See here for where to find everything.

    Post edited by RayDAnt on
  • TheKDTheKD Posts: 1,236
    edited July 23

    OK Ill play

    System Configuration
     

    System/Motherboard: GIGABYTE B450 AORUS PRO WIFI-CF

    CPU: AMD Ryzen 5 2600X @ 4.0 ghz
    GPU: MSI GTX 1070 Armor OC/Aero OC @ 1648mhz clock  2230mhz memory,  GIGABYTE GeForce GTX 960 OC 4GB @ 1276mhz clock  1810mhz memory   
    System Memory: Corsairw DDR4-3200 8gb x2   gskill DDR4-3200 8gb x2   
    OS Drive: Samsung 960 EVO 250gb
    Asset Drive: Seagate 2TB 7200 rpm
    Operating System: Microsoft Windows 7 Ultimate (x64) Build 7601 (Service Pack 1)
    Nvidia Drivers Version: 431.36
    Daz Studio Version: 4.12.0.33 x64

     

    Both GPU and CPU

    Optix Prime Acceleration: on

    TRT_STATS 9 minutes 12.87 seconds
    DEVICE_STATS (GeForce GTX 1070): 1131 iterations, 6.028s init, 544.168s render

    (GeForce GTX 960): 445 iterations, 7.191s init, 543.245s render

    CPU: 224 iterations, 3.912s init, 546.102s render
    Iteration Rate:  3.307 iterations per second
    System Overhead:  6.768 seconds 

     

    Optix Prime Acceleration: Off

    TRT_STATS  8 minutes 27.25 seconds
    DEVICE_STATS  (GeForce GTX 1070): 1161 iterations, 7.172s init, 496.600s
    (GeForce GTX 960): 444 iterations, 6.061s init, 497.486s

    CPU:      195 iterations, 3.975s init, 499.952s

    Iteration Rate: 3.619  iterations per second
    System Overhead: 10.65 seconds

     

     

     

     

    Both GPU no CPU

     

    Optix Prime Acceleration: on

    TRT_STATS 8 minutes 32.69 seconds
    DEVICE_STATS (GeForce GTX 1070): 1294 iterations, 4.460s init, 505.825s render

    (GeForce GTX 960): 506 iterations, 5.339s init, 504.821s render
    Iteration Rate: 3.560 iterations per second
    System Overhead: 6.865 seconds 

     

    Optix Prime Acceleration: Off

    TRT_STATS 8 minutes 32.89 seconds
    DEVICE_STATS (GeForce GTX 1070):  1294 iterations, 4.733s init, 504.448s

    (GeForce GTX 960): 506 iterations, 4.953s init, 504.705s
    Iteration Rate: 3.567  iterations per second
    System Overhead:  8.442 seconds

     

     

    CPU only

     

    Optix Prime Acceleration: on

    TRT_STATS  1 hours 1 minutes 53.71 seconds
    DEVICE_STATS  CPU:  1800 iterations, 3.933s init, 3706.529s render
    Iteration Rate:  0.485 iterations per second
    System Overhead: 3660 seconds

     

     

     

    1070 only

    Optix Prime Acceleration: on

    TRT_STATS  11 minutes 33.74 seconds
    DEVICE_STATS (GeForce GTX 1070): 1800 iterations, 4.181s init, 686.323s render
    Iteration Rate:  2.622 iterations per second
    System Overhead:   7.417 seconds

     

    Optix Prime Acceleration: Off

    TRT_STATS  11 minutes 32.81 seconds
    DEVICE_STATS  (GeForce GTX 1070): 1800 iterations, 4.182s init, 685.427s

    Iteration Rate: 2.626  iterations per second
    System Overhead:  7.383 seconds

     

     

    960 only

    Optix Prime Acceleration: On

    TRT_STATS  28 minutes 53.53 seconds
    DEVICE_STATS  (GeForce GTX 960): 1800 iterations, 4.320s init, 1725.972s render
    Iteration Rate: 1.042 iterations per second
    System Overhead: 7.028 seconds

     

    PS: I hate the forum formatting quirks.

    Post edited by TheKD on
  • RayDAntRayDAnt Posts: 360
    edited July 23

    TheKD, could you add runs for each GPU rendering the scene separately as well? That way we have the whole set.

    Also, it looks like the CPU stats are missing from your first test. They should be in your log file right after the info you posted. Here's an example of what it should look like:

    CPU: 	 5 iterations, 0.077s init, 0.684s render

     

    Post edited by RayDAnt on
  • TheKDTheKD Posts: 1,236
    edited July 23

    Didnt see a CPU line, so thought I missed it and ran it again. Still no CPU line. Maybe it has something to do with that new embree stuff, not sure what's up with that.

    2019-07-22 22:50:27.779 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Initializing local rendering.
    2019-07-22 22:50:27.795 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CPU: using 10 cores for rendering
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 3 device(s):
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CUDA device 0 (GeForce GTX 1070)
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CUDA device 1 (GeForce GTX 960)
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CPU
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.7   IRAY   rend info : Initializing Embree
    2019-07-22 22:50:27.810 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...
    2019-07-22 22:50:27.810 Iray VERBOSE - module:category(IRAY:RENDER):   1.3   IRAY   rend progr: CUDA device 1 (GeForce GTX 960): Processing scene...
    2019-07-22 22:50:27.810 Iray VERBOSE - module:category(IRAY:RENDER):   1.4   IRAY   rend progr: CPU: Processing scene...

    The log shows that it is using cpu, but it don't show the stats at the end. NVM, I see what happened. It now appeared like 2 minutes after I closed daz studio, apparently it just takes a few minutes to show up lol. Going to redo it, and add the other 2 renders for each gpu alone.

    Post edited by TheKD on
  • RayDAntRayDAnt Posts: 360
    edited July 23
    TheKD said:

    Didnt see a CPU line, so thought I missed it and ran it again. Still no CPU line. Maybe it has something to do with that new embree stuff, not sure what's up with that.

    2019-07-22 22:50:27.779 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Initializing local rendering.
    2019-07-22 22:50:27.795 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CPU: using 10 cores for rendering
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering with 3 device(s):
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CUDA device 0 (GeForce GTX 1070)
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CUDA device 1 (GeForce GTX 960)
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info :     CPU
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : Rendering...
    2019-07-22 22:50:27.810 Iray INFO - module:category(IRAY:RENDER):   1.7   IRAY   rend info : Initializing Embree
    2019-07-22 22:50:27.810 Iray VERBOSE - module:category(IRAY:RENDER):   1.2   IRAY   rend progr: CUDA device 0 (GeForce GTX 1070): Processing scene...
    2019-07-22 22:50:27.810 Iray VERBOSE - module:category(IRAY:RENDER):   1.3   IRAY   rend progr: CUDA device 1 (GeForce GTX 960): Processing scene...
    2019-07-22 22:50:27.810 Iray VERBOSE - module:category(IRAY:RENDER):   1.4   IRAY   rend progr: CPU: Processing scene...

    The log shows that it is using cpu, but it don't show the stats at the end. NVM, I see what happened. It now appeared like 2 minutes after I closed daz studio, apparently it just takes a few minutes to show up lol. Going to redo it, and add the other 2 renders for each gpu alone.

    Awesome! Yeah, it's a little known fact that Iray functions almost completely independently of Daz Studio and oftentimes doesn't fully shut down until well after Daz Studio itself is closed.

     

    ETA: And if you're feeling really adventurous, you could do a run with just your CPU as well (would love to see more AMD CPU benchmarks out there.)

    Post edited by RayDAnt on
  • outrider42outrider42 Posts: 1,917
    edited July 23

    Just to note, that's a lot of system info to ask for. A lot of people don't even know how to find their part info. I very seriously doubt the motherboard, RAM, and hard drives play any role in rendering, and as you will see, there is small problem with the bench I will get into. But here is my info. 

    System/Motherboard: Asus Z-97
    CPU: i5-4690k @3.5ghz
    GPU: MSI Gaming 1080ti @ 1999 Mhz + EVGA SC 1080ti  @ 1980 Mhz  (very minor overclocks)
    System Memory: 32 GB DDR3 1866 Mhz
    OS Drive: Samsung 860 Evo 1 TB

    Asset Drive:  WD 4TB Black, Samsung 860 EVO 1TB
    Operating System: Win 10 1809
    Nvidia Drivers Version: 431.36 Gaming
    Daz Studio Version: 4.12 beta

     

    OptiX ON

    2019-07-23 00:39:01.369 Total Rendering Time: 4 minutes 1.76 seconds

    Optix OFF TEXTURE SHADED

    2019-07-23 00:31:57.418 Total Rendering Time: 4 minutes 2.32 seconds

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1080 Ti): 903 iterations, 5.932s init, 233.194s render

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 1 (GeForce GTX 1080 Ti): 897 iterations, 6.268s init, 233.163s render

    So...I beat the RTX Titan with two 1080tis? If I am reading this right, that is not a good sign for RTX after all.

    Anyway, here is the issue I think is going one with users. You ask users to have Texture Shaded on for the Viewport. However, this adds the loading time into the data, and loading times can vary based on other hardware. The new 4.12 beta loads much faster than any previous Daz, and this is giving people false impressions that they are getting faster, because this cuts about 30 or so seconds off the time that previous versions might take. I believe it why the person with the 2x 1070's is so happy right now in the SY bench, but their time is reflective of this faster loading more than the actual render speed. Using the Iray Preview equalizes this loading time, and thus eliminates unknown variables and better tests pure GPU rendering speed. That is why sickleyield asked people to use the Iray Viewport.

    Post edited by outrider42 on
  • Dim ReaperDim Reaper Posts: 433

    I had some spare time this morning, so I ran a few rounds of the benchmark.  I am really interested to see more RTX results to see what difference enabling it in iray now makes.

    I've run the results with 2 graphics cards, both separate and together, in DS 4.11.0.383 and in DS 4.12.33

     

    System Configuration
    System/Motherboard: ASUS X99-S
    CPU: Intel i7 5960X @3GHz
    System Memory: 32GB KINGSTON HYPER-X PREDATOR QUAD-DDR4
    OS Drive: Samsung M.2 SSD 960 EVO 250GB
    Asset Drive: 2TB WD CAVIAR BLACK  SATA 6 Gb/s, 64MB CACHE (7200rpm)
    Operating System: Windows 10.0.17 134 Build 17134
    Nvidia Drivers Version: 430.64


    Benchmark Results – 980Ti Only
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: Yes
    Total Rendering Time: 14 minutes 26.48 seconds
    CUDA device 1 (GeForce GTX 980 Ti):      1800 iterations, 3.517s init, 859.525s render
    Iteration Rate: (1800/859.525) = 2.094 iterations per second
    System Overhead: ((0+840+26.48)-859.525) =6.955 seconds

    Benchmark Results – 1080Ti Only
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: Yes
    Total Rendering Time: 8 minutes 59.70 seconds
    CUDA device 0 (GeForce GTX 1080 Ti):      1800 iterations, 3.764s init, 532.429s render
    Iteration Rate: (1800/532.429) = 3.381 iterations per second
    System Overhead: ((0+480+59.7)-532.429) = 7.271 seconds

    Benchmark Results – 980Ti + 1080Ti
    Daz Studio Version: 4.11.0.383 64-bit
    Optix Prime Acceleration: Yes
    Total Rendering Time:  5 minutes 43.5 seconds
    CUDA device 0 (GeForce GTX 1080 Ti):      1111 iterations, 3.537s init, 335.483s render
    CUDA device 1 (GeForce GTX 980 Ti):      689 iterations, 3.913s init, 335.669s render
    Iteration Rate: (1800/335.483) = 5.365 iterations per second
    System Overhead: ((0+300+43.5)-335.483) = 8.017 seconds
     


    Benchmark Results – 980Ti Only
    Daz Studio Version: 4.12.033 64-bit
    Optix Prime Acceleration: Yes
    Total Rendering Time: 11 minutes 43.96 seconds
    CUDA device 1 (GeForce GTX 980 Ti):      1800 iterations, 4.188s init, 695.982s render
    Iteration Rate: (1800/695.982) = 2.586 iterations per second
    System Overhead: ((0+660+43.96)-695.982) = 7.978 seconds

    Benchmark Results – 1080Ti Only
    Daz Studio Version: 4.12.033 64-bit
    Optix Prime Acceleration: Yes
    Total Rendering Time: 7 minutes 45.3 seconds
    CUDA device 0 (GeForce GTX 1080 Ti):      1800 iterations, 3.953s init, 457.279s render
    Iteration Rate: (1800/457.279) = 3.936 iterations per second
    System Overhead: ((0+420+45.3)-457.279) = 8.021 seconds

    Benchmark Results – 980Ti + 1080Ti
    Daz Studio Version: 4.12.033 64-bit
    Optix Prime Acceleration: Yes
    Total Rendering Time: 4 minutes 49.52 seconds
    CUDA device 0 (GeForce GTX 1080 Ti):      1084 iterations, 3.760s init, 281.346s render
    CUDA device 1 (GeForce GTX 980 Ti):      716 iterations, 4.074s init, 281.616s render
    Iteration Rate: (1800/281.616) = 6.392 iterations per second
    System Overhead: ((0+240+49.52)-281.616) = 7.904 seconds

     

  • Dim ReaperDim Reaper Posts: 433

    With the multiple tests, I found the formatting of the information for this thread a little time-consuming, so I put together a spreadsheet where I could paste the information form the log file and have it show the calculations etc.  If this is useful to anyone else, please download below.  This is in .xlsx format.  It will calculate for two cards at a time - I've left the info for my 980Ti on the first row for reference.

    xlsx
    xlsx
    Iray Benchmark Calculator.xlsx
    15K
  • LCJDLCJD Posts: 12
    RayDAnt said:

    LCJD, can you add the rest of the info (check the post before yours) to your post? Just Total Rendering Time isn't enough to caculate a final result for this benchmark. See here for where to find everything.

    Bench result updated

  • RayDAntRayDAnt Posts: 360
    edited July 23

    I very seriously doubt the motherboard, RAM, and hard drives play any role in rendering,

    They play a direct role in scene Loading Time, which is one of the main things this benchmark is designed to measure (other than pure rendering time.)

     

    So...I beat the RTX Titan with two 1080tis?

    Yes, you're reading that right. Your particular two 1080ti's slightly beat a single watercooled Titan RTX with full RTX support.

    If I am reading this right, that is not a good sign for RTX after all.

    The Titan RTX costs as much as it does because of how much memory it has - not because of how fast it is.

     

    You ask users to have Texture Shaded on for the Viewport.

    Because it's the Daz Studio default mode.

     

    However, this adds the loading time into the data,

    It adds loading time to the Loading Time statistic and nothing else as long as you include Device Statistics with your results. Hence why this benchmark asks for Device Statistics in addition to Total Rendering Time. As long as both things are reported measured rendering times are unaffected one way or another. The reason why the results you've posted so far:

    OptiX ON

    2019-07-23 00:39:01.369 Total Rendering Time: 4 minutes 1.76 seconds

    Optix OFF TEXTURE SHADED

    2019-07-23 00:31:57.418 Total Rendering Time: 4 minutes 2.32 seconds

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1080 Ti): 903 iterations, 5.932s init, 233.194s render

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 1 (GeForce GTX 1080 Ti): 897 iterations, 6.268s init, 233.163s render

    Seem to indicate what you're saying is because you are missing Device Statistics for your first test case (OptiX On, Iray viewport.) Total Rendering Time can change significantly under different viewport modes. Render time under Device Statistics doesn't. Hence why we need to know both.

     

    ETA: See this post. Something seems to be wrong with your 4.12 Beta installation in general.

    Post edited by RayDAnt on
  • allinn1000allinn1000 Posts: 0

    System Configuration
    System/Motherboard: Asus ROG Strix X570-F
    CPU: AMD Ryzen 7 3700x @stock
    GPU: Asus GeForce RTX 2080 Ti Turbo @stock
    System Memory: Corsair Vengeance LPX 32GB DDR4 @3200Mhz
    OS Drive: Samsung SSD 860 QVO 1TB
    Asset Drive: same
    Operating System: Win 10 Pro version 1903 build 18362.239
    Nvidia Drivers Version: Nvidia Studio Driver Version 430.86
    Daz Studio Version: 4.12.0.33 64-bit
    Optix Prime Acceleration: On

    Benchmark Results
    TRT_STATS: 4 minutes 30.29 seconds
    DEVICE_STATS: 1800 iterations, 2.193s init, 265.272s render
    Rendering Performance:(1800 / 265.272) = 6.785 iterations per second
    Preload Time: ((240 + 30.29) - 265.272) = 5.018 seconds

  • TheKDTheKD Posts: 1,236
    edited July 23

    Added some more, if I remember I am going to try cpu with optix off when I go to sleep or eat supper for completion sake.

    Post edited by TheKD on
  • RayDAntRayDAnt Posts: 360
    TheKD said:

    Added some more, if I remember I am going to try cpu with optix off when I go to sleep or eat supper for completion sake.

    The more the merrier! 

     

    With the multiple tests, I found the formatting of the information for this thread a little time-consuming, so I put together a spreadsheet where I could paste the information form the log file and have it show the calculations etc.  If this is useful to anyone else, please download below.  This is in .xlsx format.  It will calculate for two cards at a time - I've left the info for my 980Ti on the first row for reference.

    General Question:

    Should I remove those calculations entirely from the part you guys have to report? As long as Total Rendering Time and Device Statistics are there, I can just compute Rendering Performance and Loading Time for the graphs myself.

  • Dim ReaperDim Reaper Posts: 433
    RayDAnt said:
    TheKD said:

    Added some more, if I remember I am going to try cpu with optix off when I go to sleep or eat supper for completion sake.

    The more the merrier! 

     

    With the multiple tests, I found the formatting of the information for this thread a little time-consuming, so I put together a spreadsheet where I could paste the information form the log file and have it show the calculations etc.  If this is useful to anyone else, please download below.  This is in .xlsx format.  It will calculate for two cards at a time - I've left the info for my 980Ti on the first row for reference.

    General Question:

    Should I remove those calculations entirely from the part you guys have to report? As long as Total Rendering Time and Device Statistics are there, I can just compute Rendering Performance and Loading Time for the graphs myself.

    I would say leave them in for the added information.  It was only fiddly for me because I ran 6 benchmarks.

  • outrider42outrider42 Posts: 1,917

    I found the line 

    misc info : Iray RTX 2019.1.1, build 317500.2554, 08 Jun 2019, nt-x86-64.

    RayDAnt said:

    I very seriously doubt the motherboard, RAM, and hard drives play any role in rendering,

    They play a direct role in scene Loading Time, which is one of the main things this benchmark is designed to measure (other than pure rendering time.)

     

    So...I beat the RTX Titan with two 1080tis?

    Yes, you're reading that right. Your particular two 1080ti's slightly beat a single watercooled Titan RTX with full RTX support.

    If I am reading this right, that is not a good sign for RTX after all.

    The Titan RTX costs as much as it does because of how much memory it has - not because of how fast it is.

     

    You ask users to have Texture Shaded on for the Viewport.

    Because it's the Daz Studio default mode.

     

    However, this adds the loading time into the data,

    It adds loading time to the Loading Time statistic and nothing else as long as you include Device Statistics with your results. Hence why this benchmark asks for Device Statistics in addition to Total Rendering Time. As long as both things are reported measured rendering times are unaffected one way or another. The reason why the results you've posted so far:

    OptiX ON

    2019-07-23 00:39:01.369 Total Rendering Time: 4 minutes 1.76 seconds

    Optix OFF TEXTURE SHADED

    2019-07-23 00:31:57.418 Total Rendering Time: 4 minutes 2.32 seconds

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1080 Ti): 903 iterations, 5.932s init, 233.194s render

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 1 (GeForce GTX 1080 Ti): 897 iterations, 6.268s init, 233.163s render

    Seem to indicate what you're saying is because you are missing Device Statistics for your first test case (OptiX On, Iray viewport.) Total Rendering Time can change significantly under different viewport modes. Render time under Device Statistics doesn't. Hence why we need to know both.

     

    ETA: See this post. Something seems to be wrong with your 4.12 Beta installation in general.

    I used the texture viewport for both of these runs. I simply forgot to grab the device stats line for the first. Looking at these times, though, if I did something wrong, then I don't see how I would beat the Titan at all. If Iray is a little faster now, but I am not seeing this performance gain because I did something wrong, it would be logical that I should not be near your RTX time to begin with. Also, if RTX is any factor, again, I shouldn't be so close. But both of my times beat the Titan here. Also Titan RTX isn't just about its 24gb VRAM though that is its big draw, it has more of all 3 core types than the 2080ti.

    When I ran the tests with the Iray viewport, my total render times dropped below the 4 minute mark. But I did not post these.

    I feel that trying to measure anything besides GPU rendering in the same place is a wild goose chase. There are too many variables to ever get good data on that. Being that nearly all of us are on PC, every single machine can be unique.

  • RayDAntRayDAnt Posts: 360
    edited July 23

    I found the line 

    misc info : Iray RTX 2019.1.1, build 317500.2554, 08 Jun 2019, nt-x86-64.

    RayDAnt said:

    I very seriously doubt the motherboard, RAM, and hard drives play any role in rendering,

    They play a direct role in scene Loading Time, which is one of the main things this benchmark is designed to measure (other than pure rendering time.)

     

    So...I beat the RTX Titan with two 1080tis?

    Yes, you're reading that right. Your particular two 1080ti's slightly beat a single watercooled Titan RTX with full RTX support.

    If I am reading this right, that is not a good sign for RTX after all.

    The Titan RTX costs as much as it does because of how much memory it has - not because of how fast it is.

     

    You ask users to have Texture Shaded on for the Viewport.

    Because it's the Daz Studio default mode.

     

    However, this adds the loading time into the data,

    It adds loading time to the Loading Time statistic and nothing else as long as you include Device Statistics with your results. Hence why this benchmark asks for Device Statistics in addition to Total Rendering Time. As long as both things are reported measured rendering times are unaffected one way or another. The reason why the results you've posted so far:

    OptiX ON

    2019-07-23 00:39:01.369 Total Rendering Time: 4 minutes 1.76 seconds

    Optix OFF TEXTURE SHADED

    2019-07-23 00:31:57.418 Total Rendering Time: 4 minutes 2.32 seconds

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 0 (GeForce GTX 1080 Ti): 903 iterations, 5.932s init, 233.194s render

    2019-07-23 00:32:04.070 Iray INFO - module:category(IRAY:RENDER):   1.0   IRAY   rend info : CUDA device 1 (GeForce GTX 1080 Ti): 897 iterations, 6.268s init, 233.163s render

    Seem to indicate what you're saying is because you are missing Device Statistics for your first test case (OptiX On, Iray viewport.) Total Rendering Time can change significantly under different viewport modes. Render time under Device Statistics doesn't. Hence why we need to know both.

     

    ETA: See this post. Something seems to be wrong with your 4.12 Beta installation in general.

    I used the texture viewport for both of these runs. I simply forgot to grab the device stats line for the first.

    Could you add them in to your first run? That way I can integrate it into the tables at the top.

     

    Looking at these times, though, if I did something wrong, then I don't see how I would beat the Titan at all. If Iray is a little faster now, but I am not seeing this performance gain because I did something wrong, it would be logical that I should not be near your RTX time to begin with.

    Assuming your DS 4.12 install is good, there's no reason to think that there's anything wrong with your results. It is entirely plausible for 2 1080ti's to come out ahead of a single Titan RTX due to sheer Cuda core counts alone (the Titan RTX has 4,608 - two 1080ti's have a combined 8,704.) And although Turing Cuda cores are significantly faster than Pascal ones, they aren't that much faster.

    And RTX acceleration is unfortunately only a limited boon where this particular benchmarking scene (and others similar to it like the one that you did) are concerned because of the design constraints (see "memory requirements" under 4.1 Design Factors) necessary for a single benchmarking scene to be universally runnable on recent gen hardware. I'm still collecting data on it, but it looks like the only types of scenes which get major performance uplifts from RTX acceleration are ones which take hours to render on current gen high-end cards. Meaning that it is unfortunately a feature which is highly impractical to benchmark.

     

    When I ran the tests with the Iray viewport, my total render times dropped below the 4 minute mark.

    But render times in your Device Statistics stayed fundamentally the same (check if you doubt me.) Daz Studio's Total Rendering Time - despite its name - isn't a reliable measure of Iray rendering performance. However, render time under Iray's Device Statistics is. That is the essential number to know.

    Post edited by RayDAnt on
  • Dim ReaperDim Reaper Posts: 433

    @RayDAnt - In the first table, one of the figures has been entered incorrectly.

    Currently, it reads:

    GTX 1080Ti + GTX 980Ti 6 7.904

     The 7.904 figure is the loading time for that combination.  The correct figure is 6.392.  I noticed because currently the first table shows the 1080ti/980ti being faster than 2x1080ti.

     

    Very interesting to see some numbers for different cards.  Thank you for putting in the time to enter all of this data.  I'm considering replacing the 980TI in my system with a 2080Ti, so these figures are very useful as I make my way to a decision.

     
  • talidesadetalidesade Posts: 69

    Oops, posted this in the wrong thread. Here's my bench for 4.12 beta:

    i5 4690

    32 GB RAM

    Samsung 500MB SSD, Western Digital 1TB External

    1080ti EVGA SC2 Black 1947 mhz

    1800 iterations, 5.913s init, 457.867s render

    Total Rendering Time: 7 minutes 47.61 seconds

  • RayDAntRayDAnt Posts: 360
    edited July 24

    @RayDAnt - In the first table, one of the figures has been entered incorrectly.

    Currently, it reads:

    GTX 1080Ti + GTX 980Ti 6 7.904

     The 7.904 figure is the loading time for that combination.  The correct figure is 6.392.  I noticed because currently the first table shows the 1080ti/980ti being faster than 2x1080ti.

    Fixed it. Thanks!

     

    Very interesting to see some numbers for different cards.  Thank you for putting in the time to enter all of this data.  I'm considering replacing the 980TI in my system with a 2080Ti, so these figures are very useful as I make my way to a decision.

    Glad to hear it! That was one of the primary purposes I had here (provide useful information to people considering GPU purchases for DS/Iray use specifically.)

    Post edited by RayDAnt on
  • RayDAntRayDAnt Posts: 360
    edited July 24

    @talidesade can you add your current windows, nvidia driver, and Daz Studio versions into your post with your benchmark as well? That's the bare minimum I need to to enter your results into the tables at the top of the thread. Also whether or not you have OptiX Prime enabled (that still matters in 4.12 Beta if you have a GTX card.)

    Post edited by RayDAnt on
  • talidesadetalidesade Posts: 69
    Windows 10 1809 Nvidia 431.36 The current beta, 4.12.033 or whatever it is. Prime was disabled.
  • RayDAntRayDAnt Posts: 360
    edited September 3

    Some TCC benchmark results for those interested.

     

    System Configuration
    System/Motherboard: Gigabyte Z370 Aorus Gaming 7
    CPU: Intel i7-8700K @ stock (MCE enabled)
    GPU: Nvidia Titan RTX @ stock (watercooled)
    System Memory: Corsair Vengeance LPX 32GB DDR4 @ 3000Mhz
    OS Drive: Samsung Pro 970 512GB NVME SSD
    Asset Drive: Sandisk Extreme Portable SSD 1TB
    Operating System: Windows 10 Pro version 1903 build 18362.239 
    Nvidia Drivers Version: 431.60 GRD WDDM

     

    Benchmark Results - Titan RTX Only (TCC Mode)
    Daz Studio Version: 4.12.0.033 Beta x64
    Optix Prime Acceleration: On
    Total Rendering Time: 3 minutes 56.45 seconds
    CUDA device 0 (TITAN RTX): 1800 iterations, 2.245s init, 231.590s render
    Iteration Rate: (1800 / 231.590) = 7.772 iterations per second
    Loading Time: ((0 + 180 + 56.45) - 231.590) = (236.45 - 231.590) = 4.860 seconds

    Benchmark Results - Titan RTX Only (TCC Mode)
    Daz Studio Version: 4.11.0.383 x64
    Optix Prime Acceleration: On
    Total Rendering Time: 4 minutes 15.93 seconds
    CUDA device 0 (TITAN RTX): 1800 iterations, 2.326s init, 251.184s render
    Iteration Rate: (1800 / 251.184) = 7.166 iterations per second
    Loading Time: ((0 + 240 + 15.93) - 251.184) = (255.93 - 251.184) = 4.746 seconds

    Benchmark Results - Titan RTX Only (TCC Mode)
    Daz Studio Version: 4.11.0.383 x64
    Optix Prime Acceleration: Off
    Total Rendering Time: 4 minutes 35.57 seconds
    CUDA device 0 (TITAN RTX): 1800 iterations, 3.137s init, 270.057s render
    Iteration Rate: (1800 / 270.057) = 6.665 iterations per second
    Loading Time: ((0 + 240 + 35.57) - 270.057) = (275.57 - 270.057) = 5.513 seconds

     

    Benchmark Results - Titan RTX (TCC Mode) + Intel i7-8700K
    Daz Studio Version: 4.12.0.033 x64
    Optix Prime Acceleration: On
    Total Rendering Time: 4 minutes 5.52 seconds
    CUDA device 0 (TITAN RTX): 1693 iterations, 2.411s init, 239.909s render
    CPU: 107 iterations, 2.244s init, 240.623s render
    Iteration Rate: (1800 /  240.623) = 7.481 iterations per second
    Loading Time: ((0 + 240 + 5.52) - 240.623) = (245.52 - 240.623) = 4.897 seconds

    Benchmark Results - Titan RTX (TCC Mode) + Intel i7-8700K
    Daz Studio Version: 4.11.0.383 x64
    Optix Prime Acceleration: On
    Total Rendering Time: 4 minutes 23.24 seconds
    CUDA device 0 (TITAN RTX): 1704 iterations, 2.323s init, 257.724s render
    CPU: 96 iterations, 2.082s init, 258.780s render
    Iteration Rate: (1800 /  258.780) = 6.956 iterations per second
    Loading Time: ((0 + 240 + 23.24) - 258.780) = (263.24 - 258.780) = 4.460 seconds

    Benchmark Results - Titan RTX (TCC Mode) + Intel i7-8700K
    Daz Studio Version: 4.11.0.383 x64
    Optix Prime Acceleration: Off
    Total Rendering Time: 4 minutes 40.62 seconds
    CUDA device 0 (TITAN RTX): 1698 iterations, 3.294s init, 274.001s render
    CPU: 102 iterations, 3.022s init, 275.201s render
    Iteration Rate: (1800 /  275.201) = 6.541 iterations per second
    Loading Time: ((0 + 240 + 40.62) - 275.201) = (280.62 - 275.201) = 5.419 seconds

    Post edited by RayDAnt on
  • ebergerlyebergerly Posts: 2,842
    edited July 25

    I’ve been kinda scratching my head trying to figure out what we’re trying to accomplish with this effort. Apparently it was mentioned in another thread that we’re trying to make a comparison guide for users to see how well the cards perform to help in purchasing decisions?

    But the excellent migenius article basically says that Iray/RTX performance is totally dependent upon scene content (“complexity”), and the only way to benchmark RTX/Iray performace is by each user trying RTX/Iray out on scenes that represent their typical complexity (whatever that means) to get a rough idea. And they’re saying the performance range they’ve seen is a staggering 5% - 300%, depending on scene content.

    So why would we gather so much detailed hardware/software info to come up with a highly accurate render time comparison, down to a fraction of a second, for a single scene (which may or may not take much advantage of the RTX technology), when users’ actual results for their personal scenes could be anywhere in that 5% - 300% range? We get GPU render time comparisons accurate to 0.01 second for this benchmark scene using all of this detailed data, but a user may find their results for their particular scenes are not even close to what these benchmarks indicate. “Hey, you said there’s 300% improvement, how come I’m only getting 5% on my scenes?”.

    And it sounds like we’re trying to find the most “complex” scene in the store as a benchmark, and I doubt we even know what scene characteristics are needed to get the most RTX/Iray performance gain. And why do we even care about the complex scene and the most performance gain, when it may be irrelevant to the average user?

    Personally, I think the migenius article puts the nail in the coffin of standard, single scene benchmarks like this. Like I said long ago, this stuff is incredibly complex, and as you start to add other RTX-related features into the mix (Tensor de-noising, materials, physics), it becomes virtually impossible to find a single (or two, or three) benchmarks to be of much (any) use. My biggest surprise with the migenius article was that I wasn’t conservative enough in suggesting these benchmarks are, at best, ballparks within maybe +/- 15 seconds or 10% or whatever for comparison purposes. Wow, 5% to 300% variation? Amazing.

    Post edited by ebergerly on
  • bluejauntebluejaunte Posts: 1,320
    edited July 25

    Please post ONLY benchmark results in this thread.


    For discussion of these results or issues pertaining to benchmarking in general go here.

     

    Post edited by bluejaunte on
  • RayDAntRayDAnt Posts: 360

    ebergerly see this post.

Sign In or Register to comment.