Holomark 2 Scores (Searchable Text Results)

Rhino Windows Hardware
1

I recently tried using the Holomark 2 Released thread to research my new PC build and found it somewhat cumbersome. The result images aren’t searchable and lots of images were unavailable. Thought it might be a good idea to start another thread for people to post the text version of their results so it’s easier to consume when doing comparisons.

Here is my score for a stock install (Windows 7 x64 SP1 with all updates, Nvidia drivers, HWMonitor, Rhino 5, Holomark 2):

Holomark 2 v2,2,03

Total Score: 73478
Total Runtime: 229.18 sec

GPU scores: 55910
GPU_01 - 1111.10 fps - Cube 4 tests
GPU_02 - 45.00 fps - UDT Shape
GPU_03 - 94.30 fps - Wireframe
GPU_04 - 45.00 fps - Shaded
GPU_05 - 31.80 fps - Rendered
GPU_06 - 29.90 fps - Block Rendered
GPU_07 - 18 units Nurbs @ 5 fps in Wireframe
GPU_08 - 11 units Nurbs @ 5 fps in Shaded
GPU_09 - 33 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 212.80 fps - RenderMesh Render
GPU_11 - 500.00 fps - RenderMesh RenderSpeed
GPU_12 - 238.10 fps - JoinedMesh Render
GPU_13 - 1666.70 fps - JoinedMesh RenderSpeed
GPU_14 - 49 units mesh @ 15 fps in Shaded
GPU_15 - 11 units mesh @ 15 fps in Render
GPU_16 - 304 units mesh @ 15 fps in RenderSpeed
GPU_17 - 133.30 fps - mesh in Rendered Studio
GPU_18 - 9.90 fps - Nurbs in Rendered Studio
GPU_19 - 23.00 fps - Block Illustration
GPU_20 - 90.10 fps - 2D single
GPU_21 - 12.90 fps - 2D massive (20x)

CPU scores: 17568
CPU_01 - 7.99 sec - Booleans and Contours
CPU_02 - 0.98 sec - Twist and Taper (UDT)
CPU_03 - 3.67 sec - Meshing Mini
CPU_04 - 0.02 sec - Extract Render Mesh
CPU_05 - 0.02 sec - Join Render Mesh
CPU_06 - 10.69 sec - Reduce Mesh
CPU_07 - 2.11 sec - Calculating Technical display
CPU_08 - 2.98 sec - Making Silhouettes

To Be Filled By O.E.M.
To Be Filled By O.E.M.

NVIDIA Quadro K4200 - 4095.0 MB
DriverVersion: 9.18.13.4807

Intel(R) Core™ i7-4790K CPU @ 4.00GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 4.0 GHz

TotalPhysicalMemory: 32.0 GB

Microsoft Windows 7 Ultimate

  • Service Pack 1 - 64-bit

Rhino 5 sr 11 32 bit

After following the two Additional Quadro Performance Improvements on the McNeel wiki it broke the 80k mark (CPU scores also improved):

Holomark 2 v2,2,03

Total Score: 80208
Total Runtime: 197.37 sec

GPU scores: 59900
GPU_01 - 1290.30 fps - Cube 4 tests
GPU_02 - 60.60 fps - UDT Shape
GPU_03 - 116.30 fps - Wireframe
GPU_04 - 73.50 fps - Shaded
GPU_05 - 49.30 fps - Rendered
GPU_06 - 47.80 fps - Block Rendered
GPU_07 - 25 units Nurbs @ 5 fps in Wireframe
GPU_08 - 16 units Nurbs @ 5 fps in Shaded
GPU_09 - 33 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 123.50 fps - RenderMesh Render
GPU_11 - 909.10 fps - RenderMesh RenderSpeed
GPU_12 - 61.00 fps - JoinedMesh Render
GPU_13 - 1666.70 fps - JoinedMesh RenderSpeed
GPU_14 - 2 units mesh @ 15 fps in Shaded
GPU_15 - 4 units mesh @ 15 fps in Render
GPU_16 - 299 units mesh @ 15 fps in RenderSpeed
GPU_17 - 71.40 fps - mesh in Rendered Studio
GPU_18 - 16.30 fps - Nurbs in Rendered Studio
GPU_19 - 37.30 fps - Block Illustration
GPU_20 - 106.40 fps - 2D single
GPU_21 - 11.00 fps - 2D massive (20x)

CPU scores: 20308
CPU_01 - 7.04 sec - Booleans and Contours
CPU_02 - 0.89 sec - Twist and Taper (UDT)
CPU_03 - 3.09 sec - Meshing Mini
CPU_04 - 0.02 sec - Extract Render Mesh
CPU_05 - 0.03 sec - Join Render Mesh
CPU_06 - 9.92 sec - Reduce Mesh
CPU_07 - 1.15 sec - Calculating Technical display
CPU_08 - 2.48 sec - Making Silhouettes

To Be Filled By O.E.M.
To Be Filled By O.E.M.

NVIDIA Quadro K4200 - 4095.0 MB
DriverVersion: 9.18.13.4807

Intel(R) Core™ i7-4790K CPU @ 4.00GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 4.0 GHz

TotalPhysicalMemory: 32.0 GB

Microsoft Windows 7 Ultimate

  • Service Pack 1 - 64-bit

Rhino 5 sr 11 64 bit

Just for posterity, here is my old workstation:

Holomark 2 v2,2,03

Total Score: 25035
Total Runtime: 288.56 sec

GPU scores: 20490
GPU_01 - 449.40 fps - Cube 4 tests
GPU_02 - 22.80 fps - UDT Shape
GPU_03 - 38.30 fps - Wireframe
GPU_04 - 31.00 fps - Shaded
GPU_05 - 18.90 fps - Rendered
GPU_06 - 20.20 fps - Block Rendered
GPU_07 - 12 units Nurbs @ 5 fps in Wireframe
GPU_08 - 7 units Nurbs @ 5 fps in Shaded
GPU_09 - 20 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 54.60 fps - RenderMesh Render
GPU_11 - 163.90 fps - RenderMesh RenderSpeed
GPU_12 - 35.00 fps - JoinedMesh Render
GPU_13 - 526.30 fps - JoinedMesh RenderSpeed
GPU_14 - 3 units mesh @ 15 fps in Shaded
GPU_15 - 3 units mesh @ 15 fps in Render
GPU_16 - 94 units mesh @ 15 fps in RenderSpeed
GPU_17 - 42.20 fps - mesh in Rendered Studio
GPU_18 - 6.70 fps - Nurbs in Rendered Studio
GPU_19 - 9.70 fps - Block Illustration
GPU_20 - 35.10 fps - 2D single
GPU_21 - 5.00 fps - 2D massive (20x)

CPU scores: 4545
CPU_01 - 21.23 sec - Booleans and Contours
CPU_02 - 48.92 sec - Twist and Taper (UDT)
CPU_03 - 6.37 sec - Meshing Mini
CPU_04 - 0.29 sec - Extract Render Mesh
CPU_05 - 0.14 sec - Join Render Mesh
CPU_06 - 17.24 sec - Reduce Mesh
CPU_07 - 2.32 sec - Calculating Technical display
CPU_08 - 13.48 sec - Making Silhouettes

Supermicro
X8SAX

AMD FirePro V7900 (FireGL V) - 2048.0 MB
DriverVersion: 14.301.1010.0

Intel(R) Xeon(R) CPU W3680 @ 3.33GHz
NumberOfCores: 6 NumberOfLogicalProcessors: 12
MaxClockSpeed: 3.33 GHz

TotalPhysicalMemory: 24.0 GB

Microsoft Windows Server 2008 R2 Standard

  • Service Pack 1 - 64-bit

Rhino 5 sr 11 64 bit

1 Like
Holomark 2 R6 Scores (Searchable Text Results)
Alienware 15 & geforce gtx 1070
2

Holomark 2 v2,2,03

Total Score: 18409
Total Runtime: 201.58 sec

GPU scores: 11230
GPU_01 - 540.50 fps - Cube 4 tests
GPU_02 - 19.50 fps - UDT Shape
GPU_03 - 32.40 fps - Wireframe
GPU_04 - 21.60 fps - Shaded
GPU_05 - 15.10 fps - Rendered
GPU_06 - 14.60 fps - Block Rendered
GPU_07 - 7 units Nurbs @ 5 fps in Wireframe
GPU_08 - 5 units Nurbs @ 5 fps in Shaded
GPU_09 - 9 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 40.50 fps - RenderMesh Render
GPU_11 - 43.30 fps - RenderMesh RenderSpeed
GPU_12 - 48.10 fps - JoinedMesh Render
GPU_13 - 33.60 fps - JoinedMesh RenderSpeed
GPU_14 - 2 units mesh @ 15 fps in Shaded
GPU_15 - 3 units mesh @ 15 fps in Render
GPU_16 - 3 units mesh @ 15 fps in RenderSpeed
GPU_17 - 35.80 fps - mesh in Rendered Studio
GPU_18 - 5.00 fps - Nurbs in Rendered Studio
GPU_19 - 12.30 fps - Block Illustration
GPU_20 - 30.90 fps - 2D single
GPU_21 - 4.50 fps - 2D massive (20x)

CPU scores: 7179
CPU_01 - 19.58 sec - Booleans and Contours
CPU_02 - 6.68 sec - Twist and Taper (UDT)
CPU_03 - 9.39 sec - Meshing Mini
CPU_04 - 0.06 sec - Extract Render Mesh
CPU_05 - 0.15 sec - Join Render Mesh
CPU_06 - 23.94 sec - Reduce Mesh
CPU_07 - 3.04 sec - Calculating Technical display
CPU_08 - 6.80 sec - Making Silhouettes

Gateway
LX6810-01

NVIDIA GeForce GTX 560 Ti - 1024.0 MB
DriverVersion: 9.18.13.4788

Intel® Core™2 Quad CPU Q8200 @ 2.33GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 4
MaxClockSpeed: 2.34 GHz

TotalPhysicalMemory: 8.0 GB

Microsoft Windows 7 Home Premium

  • None - 64-bit

Rhino 5 sr 11 64 bit

3

Holomark 2 v2,2,03

Total Score: 20143
Total Runtime: 196.17 sec

GPU scores: 12800
GPU_01 - 500.00 fps - Cube 4 tests
GPU_02 - 19.80 fps - UDT Shape
GPU_03 - 33.70 fps - Wireframe
GPU_04 - 22.50 fps - Shaded
GPU_05 - 15.90 fps - Rendered
GPU_06 - 15.50 fps - Block Rendered
GPU_07 - 7 units Nurbs @ 5 fps in Wireframe
GPU_08 - 5 units Nurbs @ 5 fps in Shaded
GPU_09 - 14 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 43.50 fps - RenderMesh Render
GPU_11 - 100.00 fps - RenderMesh RenderSpeed
GPU_12 - 44.40 fps - JoinedMesh Render
GPU_13 - 100.00 fps - JoinedMesh RenderSpeed
GPU_14 - 3 units mesh @ 15 fps in Shaded
GPU_15 - 3 units mesh @ 15 fps in Render
GPU_16 - 7 units mesh @ 15 fps in RenderSpeed
GPU_17 - 42.40 fps - mesh in Rendered Studio
GPU_18 - 5.20 fps - Nurbs in Rendered Studio
GPU_19 - 13.20 fps - Block Illustration
GPU_20 - 34.50 fps - 2D single
GPU_21 - 4.20 fps - 2D massive (20x)

CPU scores: 7343
CPU_01 - 20.57 sec - Booleans and Contours
CPU_02 - 2.85 sec - Twist and Taper (UDT)
CPU_03 - 9.46 sec - Meshing Mini
CPU_04 - 0.06 sec - Extract Render Mesh
CPU_05 - 0.11 sec - Join Render Mesh
CPU_06 - 25.08 sec - Reduce Mesh
CPU_07 - 2.80 sec - Calculating Technical display
CPU_08 - 7.16 sec - Making Silhouettes

OEM
OEM

NVIDIA GeForce GTX 580 - 3072.0 MB
DriverVersion: 9.18.13.5012

Intel® Core™2 Quad CPU @ 2.40GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 4
MaxClockSpeed: 2.45 GHz

TotalPhysicalMemory: 8.0 GB

Microsoft Windows 7 Professional

  • Service Pack 1 - 64-bit

Rhino 5 sr 8 64 bit

4

Hi guys, thanks for bringing it up.

If you want to help then I would really like it if you could find a good way to store the data in a searchable way. Preferable in a Joomla extention so people could add and maintain their own data, but a “google document” ish way that has two or three administrators could also do.

I don’t have time to maintain the data for the time being so I would need the help.

It would be much better than having loads of text in unorganized order imo.

5

I can’t take on one more side project at the moment, but I was thinking if the text results were at least being captured here then later I could scrape the page and put them to a database with some passmark style reports.

6

Hi Eric, I know how that feels :wink:
And thanks for the initiative. I’ll see what I can do in the future too.

-Jørgen

7

Seriously, I’m really thankful for your plug-in. It really helped me to decide on hardware. I can hopefully do the reports for you this summer.

8

QUALITY SETTING:

Holomark 2 v2,2,03

Total Score: 59813
Total Runtime: 143.0 sec

GPU scores: 39980
GPU_01 - 1666.70 fps - Cube 4 tests
GPU_02 - 60.60 fps - UDT Shape
GPU_03 - 116.30 fps - Wireframe
GPU_04 - 76.90 fps - Shaded
GPU_05 - 47.20 fps - Rendered
GPU_06 - 45.90 fps - Block Rendered
GPU_07 - 25 units Nurbs @ 5 fps in Wireframe
GPU_08 - 16 units Nurbs @ 5 fps in Shaded
GPU_09 - 53 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 149.30 fps - RenderMesh Render
GPU_11 - 172.40 fps - RenderMesh RenderSpeed
GPU_12 - 208.30 fps - JoinedMesh Render
GPU_13 - 133.30 fps - JoinedMesh RenderSpeed
GPU_14 - 6 units mesh @ 15 fps in Shaded
GPU_15 - 11 units mesh @ 15 fps in Render
GPU_16 - 16 units mesh @ 15 fps in RenderSpeed
GPU_17 - 133.30 fps - mesh in Rendered Studio
GPU_18 - 16.30 fps - Nurbs in Rendered Studio
GPU_19 - 37.90 fps - Block Illustration
GPU_20 - 117.60 fps - 2D single
GPU_21 - 10.50 fps - 2D massive (20x)

CPU scores: 19833
CPU_01 - 7.31 sec - Booleans and Contours
CPU_02 - 0.84 sec - Twist and Taper (UDT)
CPU_03 - 3.21 sec - Meshing Mini
CPU_04 - 0.02 sec - Extract Render Mesh
CPU_05 - 0.03 sec - Join Render Mesh
CPU_06 - 10.01 sec - Reduce Mesh
CPU_07 - 1.23 sec - Calculating Technical display
CPU_08 - 2.56 sec - Making Silhouettes

ASUS
All Series

NVIDIA GeForce GTX 970 - 4095.0 MB
DriverVersion: 10.18.13.5560

Intel® Core™ i7-4790K CPU @ 4.00GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 4.0 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 7 Professional

  • Service Pack 1 - 64-bit

Rhino 5 sr 11 64 bit

PERFORMANCE SETTING:

Holomark 2 v2,2,03

Total Score: 75495
Total Runtime: 246.65 sec

GPU scores: 55350
GPU_01 - 1904.80 fps - Cube 4 tests
GPU_02 - 61.00 fps - UDT Shape
GPU_03 - 119.00 fps - Wireframe
GPU_04 - 75.20 fps - Shaded
GPU_05 - 46.70 fps - Rendered
GPU_06 - 46.50 fps - Block Rendered
GPU_07 - 25 units Nurbs @ 5 fps in Wireframe
GPU_08 - 16 units Nurbs @ 5 fps in Shaded
GPU_09 - 52 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 149.30 fps - RenderMesh Render
GPU_11 - 434.80 fps - RenderMesh RenderSpeed
GPU_12 - 212.80 fps - JoinedMesh Render
GPU_13 - 370.40 fps - JoinedMesh RenderSpeed
GPU_14 - 10 units mesh @ 15 fps in Shaded
GPU_15 - 11 units mesh @ 15 fps in Render
GPU_16 - 410 units mesh @ 15 fps in RenderSpeed
GPU_17 - 137.00 fps - mesh in Rendered Studio
GPU_18 - 16.10 fps - Nurbs in Rendered Studio
GPU_19 - 38.30 fps - Block Illustration
GPU_20 - 120.50 fps - 2D single
GPU_21 - 10.80 fps - 2D massive (20x)

CPU scores: 20145
CPU_01 - 7.16 sec - Booleans and Contours
CPU_02 - 0.86 sec - Twist and Taper (UDT)
CPU_03 - 3.15 sec - Meshing Mini
CPU_04 - 0.02 sec - Extract Render Mesh
CPU_05 - 0.03 sec - Join Render Mesh
CPU_06 - 9.89 sec - Reduce Mesh
CPU_07 - 1.20 sec - Calculating Technical display
CPU_08 - 2.51 sec - Making Silhouettes

ASUS
All Series

NVIDIA GeForce GTX 970 - 4095.0 MB
DriverVersion: 10.18.13.5560

Intel® Core™ i7-4790K CPU @ 4.00GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 4.0 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 7 Professional

  • Service Pack 1 - 64-bit

Rhino 5 sr 11 64 bit

9

Holomark 2 v2,2,03

Total Score: 28162
Total Runtime: 165.04 sec

GPU scores: 18480
GPU_01 - 714.30 fps - Cube 4 tests
GPU_02 - 27.20 fps - UDT Shape
GPU_03 - 53.20 fps - Wireframe
GPU_04 - 36.40 fps - Shaded
GPU_05 - 25.40 fps - Rendered
GPU_06 - 24.60 fps - Block Rendered
GPU_07 - 12 units Nurbs @ 5 fps in Wireframe
GPU_08 - 8 units Nurbs @ 5 fps in Shaded
GPU_09 - 24 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 92.60 fps - RenderMesh Render
GPU_11 - 66.70 fps - RenderMesh RenderSpeed
GPU_12 - 112.40 fps - JoinedMesh Render
GPU_13 - 53.20 fps - JoinedMesh RenderSpeed
GPU_14 - 3 units mesh @ 15 fps in Shaded
GPU_15 - 5 units mesh @ 15 fps in Render
GPU_16 - 6 units mesh @ 15 fps in RenderSpeed
GPU_17 - 87.70 fps - mesh in Rendered Studio
GPU_18 - 8.40 fps - Nurbs in Rendered Studio
GPU_19 - 19.50 fps - Block Illustration
GPU_20 - 53.20 fps - 2D single
GPU_21 - 5.20 fps - 2D massive (20x)

CPU scores: 9682
CPU_01 - 13.75 sec - Booleans and Contours
CPU_02 - 3.30 sec - Twist and Taper (UDT)
CPU_03 - 9.29 sec - Meshing Mini
CPU_04 - 0.05 sec - Extract Render Mesh
CPU_05 - 0.10 sec - Join Render Mesh
CPU_06 - 17.76 sec - Reduce Mesh
CPU_07 - 2.33 sec - Calculating Technical display
CPU_08 - 5.06 sec - Making Silhouettes

To be filled by O.E.M.
To be filled by O.E.M.

NVIDIA GeForce GTX 750 Ti - 2048.0 MB
DriverVersion: 10.18.13.5582

AMD FX™-8320 Eight-Core Processor
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 3.5 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 10 Pro

  • None - 64-bit

Rhino 5 sr 12 64 bit

10

Holomark 2 v2,2,03

Total Score: 29877
Total Runtime: 151.82 sec

GPU scores: 16190
GPU_01 - 465.10 fps - Cube 4 tests
GPU_02 - 40.00 fps - UDT Shape
GPU_03 - 76.90 fps - Wireframe
GPU_04 - 46.10 fps - Shaded
GPU_05 - 30.10 fps - Rendered
GPU_06 - 29.00 fps - Block Rendered
GPU_07 - 17 units Nurbs @ 5 fps in Wireframe
GPU_08 - 10 units Nurbs @ 5 fps in Shaded
GPU_09 - 26 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 38.30 fps - RenderMesh Render
GPU_11 - 99.00 fps - RenderMesh RenderSpeed
GPU_12 - 28.20 fps - JoinedMesh Render
GPU_13 - 81.30 fps - JoinedMesh RenderSpeed
GPU_14 - 3 units mesh @ 15 fps in Shaded
GPU_15 - 2 units mesh @ 15 fps in Render
GPU_16 - 8 units mesh @ 15 fps in RenderSpeed
GPU_17 - 19.20 fps - mesh in Rendered Studio
GPU_18 - 7.40 fps - Nurbs in Rendered Studio
GPU_19 - 23.60 fps - Block Illustration
GPU_20 - 71.40 fps - 2D single
GPU_21 - 7.60 fps - 2D massive (20x)

CPU scores: 13687
CPU_01 - 10.73 sec - Booleans and Contours
CPU_02 - 1.56 sec - Twist and Taper (UDT)
CPU_03 - 4.51 sec - Meshing Mini
CPU_04 - 0.02 sec - Extract Render Mesh
CPU_05 - 0.05 sec - Join Render Mesh
CPU_06 - 14.36 sec - Reduce Mesh
CPU_07 - 1.76 sec - Calculating Technical display
CPU_08 - 3.54 sec - Making Silhouettes

System manufacturer
System Product Name

NVIDIA GeForce 8800 GT - 512.0 MB
DriverVersion: 9.18.13.4181

Intel® Core™ i7-2600K CPU @ 3.40GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 3.4 GHz

TotalPhysicalMemory: 8.0 GB

Microsoft Windows 7 Professional

  • Service Pack 1 - 64 bit

Rhino 5 sr 12 64 bit

11

I ran the first time and got these results:

Holomark 2 v2,2,03

Total Score: 30795
Total Runtime: 154.03 sec

GPU scores: 17300
GPU_01 - 350.90 fps - Cube 4 tests
GPU_02 - 39.10 fps - UDT Shape
GPU_03 - 75.20 fps - Wireframe
GPU_04 - 45.90 fps - Shaded
GPU_05 - 30.10 fps - Rendered
GPU_06 - 29.40 fps - Block Rendered
GPU_07 - 17 units Nurbs @ 5 fps in Wireframe
GPU_08 - 10 units Nurbs @ 5 fps in Shaded
GPU_09 - 26 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 51.80 fps - RenderMesh Render
GPU_11 - 188.70 fps - RenderMesh RenderSpeed
GPU_12 - 39.10 fps - JoinedMesh Render
GPU_13 - 163.90 fps - JoinedMesh RenderSpeed
GPU_14 - 3 units mesh @ 15 fps in Shaded
GPU_15 - 3 units mesh @ 15 fps in Render
GPU_16 - 22 units mesh @ 15 fps in RenderSpeed
GPU_17 - 16.40 fps - mesh in Rendered Studio
GPU_18 - 9.60 fps - Nurbs in Rendered Studio
GPU_19 - 22.70 fps - Block Illustration
GPU_20 - 74.10 fps - 2D single
GPU_21 - 7.70 fps - 2D massive (20x)

CPU scores: 13495
CPU_01 - 10.85 sec - Booleans and Contours
CPU_02 - 1.69 sec - Twist and Taper (UDT)
CPU_03 - 4.66 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.05 sec - Join Render Mesh
CPU_06 - 14.27 sec - Reduce Mesh
CPU_07 - 1.77 sec - Calculating Technical display
CPU_08 - 3.73 sec - Making Silhouettes

Dell Inc.
Precision T1600

NVIDIA Quadro 600 - 1024.0 MB
DriverVersion: 9.18.13.4788

Intel® Xeon® CPU E31270 @ 3.40GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 3.4 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 7 Professional

  • Service Pack 1 - 64-bit

Rhino 5 sr 12 64 bit

Then I updated the Quadro driver and got worst results, specially on the CPU!

Holomark 2 v2,2,03

Total Score: 26819
Total Runtime: 175.33 sec

GPU scores: 18440
GPU_01 - 296.30 fps - Cube 4 tests
GPU_02 - 37.70 fps - UDT Shape
GPU_03 - 77.50 fps - Wireframe
GPU_04 - 44.40 fps - Shaded
GPU_05 - 29.90 fps - Rendered
GPU_06 - 29.20 fps - Block Rendered
GPU_07 - 16 units Nurbs @ 5 fps in Wireframe
GPU_08 - 9 units Nurbs @ 5 fps in Shaded
GPU_09 - 21 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 63.30 fps - RenderMesh Render
GPU_11 - 277.80 fps - RenderMesh RenderSpeed
GPU_12 - 47.20 fps - JoinedMesh Render
GPU_13 - 256.40 fps - JoinedMesh RenderSpeed
GPU_14 - 4 units mesh @ 15 fps in Shaded
GPU_15 - 4 units mesh @ 15 fps in Render
GPU_16 - 40 units mesh @ 15 fps in RenderSpeed
GPU_17 - 18.20 fps - mesh in Rendered Studio
GPU_18 - 8.70 fps - Nurbs in Rendered Studio
GPU_19 - 21.30 fps - Block Illustration
GPU_20 - 72.50 fps - 2D single
GPU_21 - 8.00 fps - 2D massive (20x)

CPU scores: 8379
CPU_01 - 11.61 sec - Booleans and Contours
CPU_02 - 1.73 sec - Twist and Taper (UDT)
CPU_03 - 4.85 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.04 sec - Join Render Mesh
CPU_06 - 34.38 sec - Reduce Mesh
CPU_07 - 3.17 sec - Calculating Technical display
CPU_08 - 3.86 sec - Making Silhouettes

Dell Inc.
Precision T1600

NVIDIA Quadro 600 - 1024.0 MB
DriverVersion: 10.18.13.5442

Intel® Xeon® CPU E31270 @ 3.40GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 3.4 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 7 Professional

  • Service Pack 1 - 64-bit

Then I tweaked the driver definitions as suggested by McNeel Quadro Wiki and the CPU improved but it’s still not as the first time. Should I have kept the 340 driver version?

Holomark 2 v2,2,03

Total Score: 29296
Total Runtime: 168.56 sec

GPU scores: 18200
GPU_01 - 296.30 fps - Cube 4 tests
GPU_02 - 37.50 fps - UDT Shape
GPU_03 - 75.20 fps - Wireframe
GPU_04 - 43.90 fps - Shaded
GPU_05 - 29.40 fps - Rendered
GPU_06 - 28.50 fps - Block Rendered
GPU_07 - 17 units Nurbs @ 5 fps in Wireframe
GPU_08 - 9 units Nurbs @ 5 fps in Shaded
GPU_09 - 26 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 59.90 fps - RenderMesh Render
GPU_11 - 243.90 fps - RenderMesh RenderSpeed
GPU_12 - 41.70 fps - JoinedMesh Render
GPU_13 - 222.20 fps - JoinedMesh RenderSpeed
GPU_14 - 4 units mesh @ 15 fps in Shaded
GPU_15 - 3 units mesh @ 15 fps in Render
GPU_16 - 39 units mesh @ 15 fps in RenderSpeed
GPU_17 - 16.60 fps - mesh in Rendered Studio
GPU_18 - 9.30 fps - Nurbs in Rendered Studio
GPU_19 - 21.90 fps - Block Illustration
GPU_20 - 75.20 fps - 2D single
GPU_21 - 7.00 fps - 2D massive (20x)

CPU scores: 11096
CPU_01 - 11.53 sec - Booleans and Contours
CPU_02 - 1.78 sec - Twist and Taper (UDT)
CPU_03 - 4.83 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.04 sec - Join Render Mesh
CPU_06 - 20.37 sec - Reduce Mesh
CPU_07 - 2.62 sec - Calculating Technical display
CPU_08 - 3.86 sec - Making Silhouettes

Dell Inc.
Precision T1600

NVIDIA Quadro 600 - 1024.0 MB
DriverVersion: 10.18.13.5442

Intel® Xeon® CPU E31270 @ 3.40GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 3.4 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 7 Professional

  • Service Pack 1 - 64-bit

Rhino 5 sr 12 64 bit

Sorry for the long post.

12

My old laptop

Holomark 2 v2,2,03

Total Score: 12101
Total Runtime: 272.77 sec

GPU scores: 7000
GPU_01 - 146.50 fps - Cube 4 tests
GPU_02 - 13.60 fps - UDT Shape
GPU_03 - 22.70 fps - Wireframe
GPU_04 - 15.10 fps - Shaded
GPU_05 - 11.00 fps - Rendered
GPU_06 - 10.70 fps - Block Rendered
GPU_07 - 6 units Nurbs @ 5 fps in Wireframe
GPU_08 - 3 units Nurbs @ 5 fps in Shaded
GPU_09 - 9 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 29.90 fps - RenderMesh Render
GPU_11 - 90.10 fps - RenderMesh RenderSpeed
GPU_12 - 23.80 fps - JoinedMesh Render
GPU_13 - 82.00 fps - JoinedMesh RenderSpeed
GPU_14 - 1 units mesh @ 15 fps in Shaded
GPU_15 - 1 units mesh @ 15 fps in Render
GPU_16 - 11 units mesh @ 15 fps in RenderSpeed
GPU_17 - 10.50 fps - mesh in Rendered Studio
GPU_18 - 3.60 fps - Nurbs in Rendered Studio
GPU_19 - 9.20 fps - Block Illustration
GPU_20 - 22.10 fps - 2D single
GPU_21 - 3.60 fps - 2D massive (20x)

CPU scores: 5101
CPU_01 - 31.63 sec - Booleans and Contours
CPU_02 - 5.98 sec - Twist and Taper (UDT)
CPU_03 - 16.08 sec - Meshing Mini
CPU_04 - 0.20 sec - Extract Render Mesh
CPU_05 - 0.17 sec - Join Render Mesh
CPU_06 - 29.57 sec - Reduce Mesh
CPU_07 - 4.15 sec - Calculating Technical display
CPU_08 - 10.23 sec - Making Silhouettes

ASUSTeK Computer Inc.
N61Vn

NVIDIA GeForce GT 240M - 1024.0 MB
DriverVersion: 9.18.13.4181

Intel® Core™2 Quad CPU Q9000 @ 2.00GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 4
MaxClockSpeed: 2.0 GHz

TotalPhysicalMemory: 4.0 GB

Microsoft Windows 10 Pro

  • None - 64 bits

Rhino 5 sr 9 64 bit

13

Hm… if this is correct then why would the driver affect Reduce Mesh and Calculate Technical Display Mode?
@John_Brock can this be true, and any ideas what’s causing it?

14

I don’t know the details of how the OpenGL pipelines are used in ReduceMesh and in Technical Display mode.
I suspect ReduceMesh would only use OpenGL for command preview feedback.
Technical display is based on OpenGL “trickery” so it would potentially be more effected by the drivers.

My general approach when I suspect I have an OpenGL related problem, it to turn off accelerated hardware modes in Rhino options, restart Rhino, and try to repeat the problem. If the issue goes away with AH is off and comes back when AH is on, I’m pretty sure the problem is related to OpenGL support on my computer.

Perhaps @stevebaer or @jeff would have better insight on these specifics.

15

But turning off acceleration isn’t going to prove anything here…He’s getting slower speeds than before, it’s not that things aren’t working.

However, JB is correct about Technical Display using OpenGL for trickery. In order to draw specific things like hidden lines and silhouettes, the Technical Display makes several passes through the database, rendering several different frames and extracting information from the results…you don’t see that as a user, except in the form of dotted lines and silhouette lines…There are other passes as well, I just don’t want to mention all of them here. So in the end, if your display performance has been altered in any way, then Technical Display mode calculations will also be altered.

16

Hi Jeff, just to be clear, I wrote Holomark so to calculate Technical Display data it turns on the displaymode and turns it off again as soon as it can, so in theory it would draw just one frame after the Technical Display mode calculations are done, This is CPU_07, so should (could?)that cause a jump from 1.7 to 3.2 seconds in calculation time?
Benchmarking the use of the Technical Display mode is “GPU_19 - Block Illustration” and goes from 23.6 fps to 22.7 fps so to me it seems like the use of the displaymode is only a tad slower, and could be caused by other factors at runtime.

CPU_05 Reduce Mesh goes from 14.3 to 24.38 but I didn’t think the display drivers could affect this, can it really?

17

Yes, but keep in mind that it draws several frames leading up to that…you just don’t ever see them…you only see one frame, the final frame once calculations have completed. I don’t know off the top of my head how many passes through the database occur, but it’s several to be sure.

Could it cause that big of a jump? … I suppose… but I personally don’t think it is. My WAG on this is that the technical display also uses OpenCL for several of its calculations to take advantage of multiple CPUs…and OpenCL is HIGHLY dependent on the drivers…and any tweak to the drivers could have significant impact on how OpenCL operates, which would then have significant impact on any code using OpenCL.

The thing that also needs top be questioned here IMO, are the initial results. Anytime you have benchmark discrepancies, you can’t just simply rely on previously captured results…(a lot of other factors could be in play)…You must go back and see if you can still replicate previous results consistently, and then confirm that the latest results still show the discrepancies. So I would, if at all possible, go back and see if you can indeed replicate the same results for CPU_07 using previous drivers…if you can, then it’s definitely something in the drivers. If you can’t, then something else obviously has changed to cause the discrepancies.

As for Reduce Mesh… I haven’t a clue…other than if it too uses OpenCL (which it very well could), then it would also suffer for the same reasons…and it would also explain why two totally unrelated pieces in Rhino see performance differences using different drivers.

-J

18

Thanks Jeff, that clears things up for me, I have seen this impact on other machines as well and this surely makes sense, I just didn’t think they neither used OpenCL nor OpenGL. That means they should not be used as CPU scores and I should fix that for the next Holomark, and I’ll check first with you guys too.

Thanks again!

19

Trying on new laptop. Is it normal that it’s listing a
"Intel® HD Graphics P530 - 1024.0 MB" when this thing has an Nvidia Quadro M5000M w/8GB?

Holomark 2 v2,2,03

Total Score: 38650
Total Runtime: 173.09 sec

GPU scores: 22300
GPU_01 - 274.00 fps - Cube 4 tests
GPU_02 - 44.80 fps - UDT Shape
GPU_03 - 76.30 fps - Wireframe
GPU_04 - 53.20 fps - Shaded
GPU_05 - 22.20 fps - Rendered
GPU_06 - 21.70 fps - Block Rendered
GPU_07 - 19 units Nurbs @ 5 fps in Wireframe
GPU_08 - 13 units Nurbs @ 5 fps in Shaded
GPU_09 - 41 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 40.50 fps - RenderMesh Render
GPU_11 - 256.40 fps - RenderMesh RenderSpeed
GPU_12 - 55.60 fps - JoinedMesh Render
GPU_13 - 333.30 fps - JoinedMesh RenderSpeed
GPU_14 - 9 units mesh @ 15 fps in Shaded
GPU_15 - 6 units mesh @ 15 fps in Render
GPU_16 - 75 units mesh @ 15 fps in RenderSpeed
GPU_17 - 24.00 fps - mesh in Rendered Studio
GPU_18 - 12.00 fps - Nurbs in Rendered Studio
GPU_19 - 27.00 fps - Block Illustration
GPU_20 - 69.00 fps - 2D single
GPU_21 - 10.00 fps - 2D massive (20x)

CPU scores: 16350
CPU_01 - 9.33 sec - Booleans and Contours
CPU_02 - 1.28 sec - Twist and Taper (UDT)
CPU_03 - 4.12 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.05 sec - Join Render Mesh
CPU_06 - 11.06 sec - Reduce Mesh
CPU_07 - 1.51 sec - Calculating Technical display
CPU_08 - 3.20 sec - Making Silhouettes

Dell Inc.
Precision 7710

Intel® HD Graphics P530 - 1024.0 MB
DriverVersion: 10.18.15.4287

Intel® Xeon® CPU E3-1535M v5 @ 2.90GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 2.9 GHz

TotalPhysicalMemory: 64.0 GB

Microsoft Windows 10 Pro

  • None - 64-bit

Rhino 5 sr 12 64 bit

20

…and here’s with my Surface Pro 4. Very similar scores in GPU. Something’s up!
Why is my Quadro in the post above dormant?

Holomark 2 v2,2,03

Total Score: 32800
Total Runtime: 188.44 sec

GPU scores: 19460
GPU_01 - 279.70 fps - Cube 4 tests
GPU_02 - 38.20 fps - UDT Shape
GPU_03 - 65.80 fps - Wireframe
GPU_04 - 48.80 fps - Shaded
GPU_05 - 31.90 fps - Rendered
GPU_06 - 29.00 fps - Block Rendered
GPU_07 - 18 units Nurbs @ 5 fps in Wireframe
GPU_08 - 13 units Nurbs @ 5 fps in Shaded
GPU_09 - 43 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 41.50 fps - RenderMesh Render
GPU_11 - 172.40 fps - RenderMesh RenderSpeed
GPU_12 - 42.70 fps - JoinedMesh Render
GPU_13 - 188.70 fps - JoinedMesh RenderSpeed
GPU_14 - 5 units mesh @ 15 fps in Shaded
GPU_15 - 4 units mesh @ 15 fps in Render
GPU_16 - 67 units mesh @ 15 fps in RenderSpeed
GPU_17 - 18.80 fps - mesh in Rendered Studio
GPU_18 - 10.60 fps - Nurbs in Rendered Studio
GPU_19 - 25.30 fps - Block Illustration
GPU_20 - 51.80 fps - 2D single
GPU_21 - 9.20 fps - 2D massive (20x)

CPU scores: 13340
CPU_01 - 11.02 sec - Booleans and Contours
CPU_02 - 1.76 sec - Twist and Taper (UDT)
CPU_03 - 4.41 sec - Meshing Mini
CPU_04 - 0.04 sec - Extract Render Mesh
CPU_05 - 0.04 sec - Join Render Mesh
CPU_06 - 14.95 sec - Reduce Mesh
CPU_07 - 1.93 sec - Calculating Technical display
CPU_08 - 3.33 sec - Making Silhouettes

Microsoft Corporation
Surface Pro 4

Intel® Iris™ Graphics 540 - 1024.0 MB
DriverVersion: 20.19.15.4364

Intel® Core™ i7-6650U CPU @ 2.20GHz
NumberOfCores: 2 NumberOfLogicalProcessors: 4
MaxClockSpeed: 2.21 GHz

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 10 Pro

  • None - 64-bit

Rhino 5 sr 12 64 bit