Don’t worry about that. The way the RAM amount is retrieved in HoloMark doesn’t always work.
1 Like
Hi guys, sorry for being so super-absent. I’m running 3 projects on the home renovating area during weekends and a bit overloaded during workfays too, just started our biggest project yet, so Holomark has to wait a bit more, but it will arrive eventually! Thanks for stepping in for me Nathan!
6 Likes
new machine! Time for my Holomark 2 results.
Holomark 2 R6 v2,61
Total Score: 506067
Total Runtime: 2268.55 sec
GPU scores: 478670
GPU_01 - 277.80 fps - Cube 4 tests
GPU_02 - 142.90 fps - UDT Shape
GPU_03 - 1666.70 fps - Wireframe
GPU_04 - 1250.00 fps - Shaded
GPU_05 - 357.10 fps - Rendered
GPU_06 - 303.00 fps - Block Rendered
GPU_07 - 1917 units Nurbs @ 5 fps in Wireframe
GPU_08 - 858 units Nurbs @ 5 fps in Shaded
GPU_09 - 234 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 588.20 fps - RenderMesh Render
GPU_11 - 1666.70 fps - RenderMesh RenderSpeed
GPU_12 - 1250.00 fps - JoinedMesh Render
GPU_13 - 2000.00 fps - JoinedMesh RenderSpeed
GPU_14 - 224 units mesh @ 15 fps in Shaded
GPU_15 - 867 units mesh @ 15 fps in Render
GPU_16 - 2387 units mesh @ 15 fps in RenderSpeed
GPU_17 - 500.00 fps - mesh in Rendered Studio
GPU_18 - 106.40 fps - Nurbs in Rendered Studio
GPU_19 - 144.90 fps - Block Illustration
GPU_20 - 355.90 fps - 2D single
GPU_21 - 212.30 fps - 2D massive (20x)
CPU scores: 27397
CPU_01 - 3.48 sec - Booleans and Contours
CPU_02 - 0.60 sec - Twist and Taper (UDT)
CPU_03 - 6.21 sec - Meshing Mini
CPU_04 - 0.02 sec - Extract Render Mesh
CPU_05 - 0.01 sec - Join Render Mesh
CPU_06 - 5.79 sec - Reduce Mesh
CPU_07 - 0.58 sec - Calculating Technical display
CPU_08 - 1.56 sec - Making Silhouettes
Gigabyte Technology Co., Ltd.
Z690 AERO G
Intel(R) UHD Graphics - 1024.0 MB
DriverVersion: 30.0.100.9837
NVIDIA RTX A5000 - 4095.0 MB
DriverVersion: 30.0.15.1295
12th Gen Intel(R) Core™ i9-12900K
NumberOfCores: 16 NumberOfLogicalProcessors: 24
MaxClockSpeed: 3.2 GHz
TotalPhysicalMemory: 64.0 GB
Microsoft Windows 11 Pro
- None - 64-Bit
Rhino 6 sr 35 64 bit
AA level = 4
I’m a happy Rhino User…
1 Like
Congratulations, you got the Crown here!
1 Like
And that perfect number indicates that you hit a limit too. Well done, and I SERIOUSLY need to sit down and complete HM3… 
4 Likes
Yeah, I am quite pleased with my setup.
Did some quick tests in Keyshot too and I have to say I hardly could believe how fast these RTX cards are…
1 Like
I had the same RAM timing issue when I purchased the wrong RAM for my laptop. Ryzen CPUs need 1.2v, not 1.35v (that’s for Intel CPUs) so my sticks were running slower because of that. I bought 1.2v (3200Mhz) and they’re running at full speed now.
Holomark 2 R6 v2,61
Total Score: 305927
Total Runtime: 1452.85 sec
GPU scores: 286770
GPU_01 - 185.20 fps - Cube 4 tests
GPU_02 - 101.00 fps - UDT Shape
GPU_03 - 1111.10 fps - Wireframe
GPU_04 - 714.30 fps - Shaded
GPU_05 - 222.20 fps - Rendered
GPU_06 - 200.00 fps - Block Rendered
GPU_07 - 1253 units Nurbs @ 5 fps in Wireframe
GPU_08 - 528 units Nurbs @ 5 fps in Shaded
GPU_09 - 143 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 357.10 fps - RenderMesh Render
GPU_11 - 769.20 fps - RenderMesh RenderSpeed
GPU_12 - 714.30 fps - JoinedMesh Render
GPU_13 - 1250.00 fps - JoinedMesh RenderSpeed
GPU_14 - 143 units mesh @ 15 fps in Shaded
GPU_15 - 312 units mesh @ 15 fps in Render
GPU_16 - 1089 units mesh @ 15 fps in RenderSpeed
GPU_17 - 263.20 fps - mesh in Rendered Studio
GPU_18 - 64.50 fps - Nurbs in Rendered Studio
GPU_19 - 75.20 fps - Block Illustration
GPU_20 - 203.70 fps - 2D single
GPU_21 - 118.90 fps - 2D massive (20x)
CPU scores: 19157
CPU_01 - 4.98 sec - Booleans and Contours
CPU_02 - 1.04 sec - Twist and Taper (UDT)
CPU_03 - 8.20 sec - Meshing Mini
CPU_04 - 0.02 sec - Extract Render Mesh
CPU_05 - 0.01 sec - Join Render Mesh
CPU_06 - 8.87 sec - Reduce Mesh
CPU_07 - 0.79 sec - Calculating Technical display
CPU_08 - 2.19 sec - Making Silhouettes
ASUSTeK COMPUTER INC.
ROG Strix G513QM_G513QM
NVIDIA GeForce RTX 3060 Laptop GPU - 4095.0 MB
DriverVersion: 31.0.15.1693
AMD Radeon™ Graphics - 512.0 MB
DriverVersion: 30.0.13002.15001
AMD Ryzen 9 5900HX with Radeon Graphics
NumberOfCores: 8 NumberOfLogicalProcessors: 16
MaxClockSpeed: 3.3 GHz
TotalPhysicalMemory: 31.0 GB
Microsoft Windows 11 Home
- None - 64-bit
Rhino 6 sr 35 64 bit
AA level = 4
Holomark2 stops on GPU_06 Test on 3 computers.
Rhino 6.35.21222.17001 64bit Eng
Holomark2_R6 2.61
Windows 10 21h2 64 bit
PC 1: i7-9700K, MSI Z390-A PRO, 64GB 3200MHz, RTX2060, Samsung 860evo
PC 2: Ryzen 7 5800X, Gigabyte X570 Gaming X, 64GB 3200MHz, RTX2060, Samsung 870evo
PC 3: i7-11700KF, MSI MAG Z590 TORPEDO, 64GB 3600MHz, RTX3060, Samsung 870evo
I’ve tried with Rhino 6.18.19266.14201 64bit Eng, but Holomark2 stops on GPU_06 Test too.
I’ve tried to update GPU drivers to last version, but it doesn’t help.
There isn’t any antivirus software, Windows Defender is disabled.
But Holomark2 is perfectly works on PC 4 with same Windows and software configuration:
PC 4: i5-3570, MSI Z77A-G43, 32GB 1600MHz, GT 640, Kingston SUV400S37240G
UPDATE 1: I’ve tried Rhino 5.14.522.8390 64bit Eng + Holomark2 2.2.03 on PC 3, and Holomark2 is finished with results, it works!
Log:
Loading Rhino Render, version 1.50, Aug 11 2021, 00:25:18
Command: HoloMark2_R6
Preparing Holomark 2 R6 v2,61
Rhino 6 sr 35 64 bit
Starting Holomark2
Rhino’s language is English
1, C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HoloMark2_Mini_black.3dm
HoloMark2_Mini_black.3dm was located
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HM2_V6_Wire.ini
HM2_V6_Wire.ini was located
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HM2_V6_Shaded.ini
HM2_V6_Shaded.ini was located
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HM2_V6_Render.ini
HM2_V6_Render.ini was located
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HM2_V6_Illustration.ini
HM2_V6_Illustration.ini was located
C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HM2_V6_RenderSpeed.ini
HM2_V6_RenderSpeed.ini was located
All is ok
Command
Command
Command
Time to regen viewport 10 times = 0.00 seconds. (0.00 FPS)
Command
Command
HM2_V6_Wire is installed!
Command
HM2_V6_Shaded is installed!
Command
HM2_V6_Render is installed!
Command
HM2_V6_Illustration is installed!
Command
HM2_V6_RenderSpeed is installed!
Creating meshes… Press Esc to cancel
GPU_01 Cube 4 tests took :2.25 sec @ 224.7 fps.
Command
Command
Command
Time to regen viewport 10 times = 0.02 seconds. (625.00 FPS)
Calculating Contours… Press Esc to cancel
CPU_01 Booleans and Contours took :4.67 sec
CPU_02 UDT Shape took :0.75 sec
Creating meshes… Press Esc to cancel
GPU_02 Test took :0.92 sec @ 108.7 fps.
Command
Command
Command
Time to regen viewport 10 times = 0.02 seconds. (625.00 FPS)
Command: -_Import
Name of the file to import ( Browse ): “C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HoloMark2_Mini_black.3dm”
Import scaling: Keep ( DimensionNumbers ): _Enter
Import scaling: Keep ( DimensionNumbers )
Successfully read file “C:\Program Files\Common Files\McNeel\Rhinoceros\6.0\Plug-ins\Holomark2_R6 (6733c793-b8cd-f362-2097-bda699f6f4ac)\1.0.6927.1052\Holomark2_R6\Rhino 6.0\HoloMark2_Mini_black.3dm”
Command: _Enter
Can not close the last viewport
Can not close the last viewport
Can not close the last viewport
Command
Creating meshes… Press Esc to cancel
CPU_03 Meshing Rhino took :7.5 sec
GPU_03 Test took :0.08 sec @ 1250.0 fps.
GPU_04 Test took :0.11 sec @ 909.1 fps.
GPU_05 Test took :0.39 sec @ 256.4 fps.
Creating meshes… Press Esc to cancel
Mini converted to block
I noticed that happens with fast machines on clean windows installation. I suggest having a background process to run like HWinfo just to keep your CPU around 1% this should help to keep it running.
1 Like
UPDATE 2: Rhino 5.14.522.8390 64bit Eng + Holomark2 2.2.03 on PC 3, and Holomark2 was finished with results only one time. But now it stops after CPU_08.
Thank you for advice!
- I’ve tried 6.35.21222.17001 + Holomark2_R6 2.61 on PC 3 with HWinfo as background process, it doesn’t help.
- I’ve tried 6.35.21222.17001 + Holomark2_R6 2.61 on PC 3 with 7zip benchmark on 1 core as background process, it doesn’t help too.
- I’ve tried 6.35.21222.17001 + Holomark2_R6 2.61 on PC 3 under another “test” acount name, it doesn’t help too.
Can you set the refresh time of HWinfo to 50ms? This will use more cpu
1 Like
I’ve tried 2000ms, 500ms, 50ms, 20ms and it doesn’t help. 
1 Like
Frustrating, can’t wait for HM 3.0
2 Likes
While we wait for HM 3.0, here is my first try with my new RTX4090:
Total Score: 489694
GPU Score: 467860
I think I hit a few barriers though…
AA is somehow set to 2 , I will try to do a second test with AA 4
2 Likes
How did you do this? Did you have any background process running during benchmark?
I am sorry, what exactly do you mean ?
Are you referring to AA being 2? If so the answer is : I have no clue why it switched to 2 
Hi everybody!
No, I think he wonders how you made it not crash/hang.
Problem is I don’t know why this happens because it runs just fine on my machines 
And luckily we are getting closer to colder weather and less carpentering on the house, so I hope I’ll get some time to finish Holomark3. the 40xx series deserves it!
4 Likes
The #1 reason for why Holomark crashes is because of a divide-by-zero… Some tasks produce a 0.0 result, which then gets used as the divisor in a final calculation…and boom!
The 0.0’s usually show up on much faster configs, because it was never assumed that something could take 0.0s… so if you’re crashing, it means you probably have exceeded the expectations of the author 
… so it’s a good thing …LOL
There’s nothing Rhino can do about this, as this is all inside Jorgen’s script.
3 Likes