Holomark2_R6

I agree, I can run it by slowing down my PC, I ran OCCT monitoring in the background and got the results below: this thing took probably 45 minutes:

Maybe it’s enough to add decimal places in test results to avoid test hang/crash? For example, result will be 0.0000001 instead 0.000

Thanks, yes, I thought I had done that to the calculations already, but I must have missed some. I’ll see if I can find them.

1 Like

Got s New Laptop from work, and sure I’m benchmarking it,
i5 vPro (12th Gen) with Hybrid Nvidia RTX A1000

I’m really impressed with the Performance of i5 compared to It’s power consumption.

Holomark 2 R6 v2,61

Total Score: 252725
Total Runtime: 1003.26 sec

GPU scores: 223140
GPU_01 - 784.30 fps - Cube 4 tests
GPU_02 - 113.60 fps - UDT Shape
GPU_03 - 769.20 fps - Wireframe
GPU_04 - 588.20 fps - Shaded
GPU_05 - 212.80 fps - Rendered
GPU_06 - 200.00 fps - Block Rendered
GPU_07 - 766 units Nurbs @ 5 fps in Wireframe
GPU_08 - 474 units Nurbs @ 5 fps in Shaded
GPU_09 - 196 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 303.00 fps - RenderMesh Render
GPU_11 - 625.00 fps - RenderMesh RenderSpeed
GPU_12 - 526.30 fps - JoinedMesh Render
GPU_13 - 1111.10 fps - JoinedMesh RenderSpeed
GPU_14 - 85 units mesh @ 15 fps in Shaded
GPU_15 - 252 units mesh @ 15 fps in Render
GPU_16 - 632 units mesh @ 15 fps in RenderSpeed
GPU_17 - 212.80 fps - mesh in Rendered Studio
GPU_18 - 83.30 fps - Nurbs in Rendered Studio
GPU_19 - 108.70 fps - Block Illustration
GPU_20 - 243.30 fps - 2D single
GPU_21 - 135.00 fps - 2D massive (20x)

CPU scores: 29585
CPU_01 - 4.18 sec - Booleans and Contours
CPU_02 - 0.72 sec - Twist and Taper (UDT)
CPU_03 - 2.10 sec - Meshing Mini
CPU_04 - 0.01 sec - Extract Render Mesh
CPU_05 - 0.02 sec - Join Render Mesh
CPU_06 - 7.11 sec - Reduce Mesh
CPU_07 - 0.90 sec - Calculating Technical display
CPU_08 - 1.86 sec - Making Silhouettes

HP
HP ZBook Power 15.6 inch G9 Mobile Workstation PC

Intel(R) UHD Graphics - 1024.0 MB
DriverVersion: 31.0.101.3358
NVIDIA RTX A1000 Laptop GPU - 4095.0 MB
DriverVersion: 31.0.15.1740

12th Gen Intel(R) Core™ i5-12600H
NumberOfCores: 12 NumberOfLogicalProcessors: 16
MaxClockSpeed: 2.7 GHz

TotalPhysicalMemory: 32.0 GB

Microsoft Windows 11 Pro

  • None - 64-bit

Rhino 6 sr 35 64 bit
AA level = 4


more details

Here is a new install file to test out, this is BETA right now:
Holomark2_R6_2,63.rhi (7.2 MB)

image

This is version 2.63
(fixed a “divide by zero” bug on too fast systems.)
((known bug: I just notised this note from last installer, so this hasn’t been fixed:
The uninstaller of display modes does not work yet. I’ll work on it and post an update soon))

I AM NOT SURE IT WORKS ON V6 as I I don’t have it installed on this machine, but I used an older RhinoCommon.dll when I compiled it so it “should” work.
Please test and give feedback.

4 Likes

Hi,
My score Rhino 7
Having had a win10 64 bit pro rebuild of my tower , with all new hardware,
64Gb DDR4 Corsair Vengeance Pro memory. SSD for all internal drives.
NVIDIA GeForce RTX 3070 - 4095.0 MB
AMD Ryzen 7 5700X 8-Core Processor
then install Rhino V7,
I was interested to see how this build fares compared to others.
Please let me know how it is, where am I on the podium !

Here is my score :-

Holomark 2 R6 v2,63

Total Score: 319903
Total Runtime: 1012.32 sec

GPU scores: 298600
GPU_01 - 171.70 fps - Cube 4 tests
GPU_02 - 108.70 fps - UDT Shape
GPU_03 - 1666.70 fps - Wireframe
GPU_04 - 1250.00 fps - Shaded
GPU_05 - 277.80 fps - Rendered
GPU_06 - 222.20 fps - Block Rendered
GPU_07 - 940 units Nurbs @ 5 fps in Wireframe
GPU_08 - 538 units Nurbs @ 5 fps in Shaded
GPU_09 - 116 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 526.30 fps - RenderMesh Render
GPU_11 - 1111.10 fps - RenderMesh RenderSpeed
GPU_12 - 1111.10 fps - JoinedMesh Render
GPU_13 - 2000.00 fps - JoinedMesh RenderSpeed
GPU_14 - 112 units mesh @ 15 fps in Shaded
GPU_15 - 420 units mesh @ 15 fps in Render
GPU_16 - 1591 units mesh @ 15 fps in RenderSpeed
GPU_17 - 454.50 fps - mesh in Rendered Studio
GPU_18 - 59.90 fps - Nurbs in Rendered Studio
GPU_19 - 92.60 fps - Block Illustration
GPU_20 - 452.50 fps - 2D single
GPU_21 - 169.20 fps - 2D massive (20x)

CPU scores: 21303
CPU_01 - 3.51 sec - Booleans and Contours
CPU_02 - 0.99 sec - Twist and Taper (UDT)
CPU_03 - 7.60 sec - Meshing Mini
CPU_04 - 0.06 sec - Extract Render Mesh
CPU_05 - 0.02 sec - Join Render Mesh
CPU_06 - 8.30 sec - Reduce Mesh
CPU_07 - 0.79 sec - Calculating Technical display
CPU_08 - 2.20 sec - Making Silhouettes

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

NVIDIA GeForce RTX 3070 - 4095.0 MB
DriverVersion: 31.0.15.3179

AMD Ryzen 7 5700X 8-Core Processor
NumberOfCores: 8 NumberOfLogicalProcessors: 16
MaxClockSpeed: 3.4 GHz

TotalPhysicalMemory: 64.0 GB

Microsoft Windows 10 Pro

  • None - 64-bit

Rhino 7 sr 24 64 bit
AA level = 4

so how was this ?

Cheers
Steve

2 Likes

This looks like a very good system :+1:

1 Like

Shouldnt the 3070 have 8GB VRAM?

It does - Holomark reports anything over 4GB as 4GB.

1 Like

True, it uses a simple (old) windows registry check and that’s limited to 4gb. I have to figure out how to get the full info. If anybody knows how then please shout out :sweat_smile:

Iterate over the list of Rhino.GpuDeviceInfo returned by Rhino.DisplayDeviceInfo.GpuDeviceInfos().

You’ll get access to the amount of memory in bytes through the property Memory, and a human-readable formatted string through the property MemoryAsString. There is also Name, Vendor and DriverDateAsString.

Looks like this has been in since Rhino 7.3

2 Likes

Nice, thanks, I’ll look into it. Does it work with intels gpus as well?
(And do you know if it works with macs too?)

I don’t know if it works on the Mac, but on Windows it will report any GPU it finds.

1 Like

Thanks, and it statest this in the link you provided so I guess only windows :slight_smile:
" GpuDeviceInfo class
Represents a GPU device providing name, vendor and memory all as strings. Currently fully implemented only on Windows."

1 Like

1 Like

Holly Molly!
It’s amazing that you achieved this without encountering a division by zero error. This could be a Guinness World Record!

That is an interesting windows edition…

1 Like

The 2.63 version has a divide by zero bug fix, have you tried it?

yeah I think I got a couple of CPU errors, I’ll give it a second try

1 Like