Holomark2_R6

BauerNaval · January 2, 2019, 3:19pm

Hi,
after installing Orca for Rhino, Express marine and several more plugins and net framework 3.5 the brandnew Laptop slowed down to 165782 points.
I think this is still great for a Laptop, but annoying when it was so fast first.
Any tips?

jeff · January 2, 2019, 5:02pm

I guess the first thing I would try is to load protect all of the said plugins that you’ve installed, and see if your speeds return… If so, start turning on the plugins one at a time to see if it’s any one plugin causing the performance hit, or if it’s a combination of some/all of them.

-J

cokerone1214 · January 2, 2019, 6:01pm

Hello guys! I just bought a new laptop and tried to run holomark 2 in rhino 6. Although I have a query related to CPU. The laptop has an I7-8850H ( six core 2.6ghz, 4.3Ghz Turbo ). When I run the Holomark it shows me as a result that my cpu run at 2.6Ghz. So why during the benchmark it didnt run in higher frequency than 2.6 to reach the turbo frequency?

Thank you!

laurent_delrieu · January 2, 2019, 6:36pm

Holomark 2 R6 v2,61

Total Score: 138775
Total Runtime: 551.09 sec

GPU scores: 118250
GPU_01 - 506.30 fps - Cube 4 tests
GPU_02 - 66.70 fps - UDT Shape
GPU_03 - 370.40 fps - Wireframe
GPU_04 - 294.10 fps - Shaded
GPU_05 - 108.70 fps - Rendered
GPU_06 - 105.30 fps - Block Rendered
GPU_07 - 412 units Nurbs @ 5 fps in Wireframe
GPU_08 - 185 units Nurbs @ 5 fps in Shaded
GPU_09 - 114 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 142.90 fps - RenderMesh Render
GPU_11 - 322.60 fps - RenderMesh RenderSpeed
GPU_12 - 333.30 fps - JoinedMesh Render
GPU_13 - 714.30 fps - JoinedMesh RenderSpeed
GPU_14 - 49 units mesh @ 15 fps in Shaded
GPU_15 - 206 units mesh @ 15 fps in Render
GPU_16 - 469 units mesh @ 15 fps in RenderSpeed
GPU_17 - 144.90 fps - mesh in Rendered Studio
GPU_18 - 38.30 fps - Nurbs in Rendered Studio
GPU_19 - 34.20 fps - Block Illustration
GPU_20 - 74.00 fps - 2D single
GPU_21 - 11.40 fps - 2D massive (20x)

CPU scores: 20525
CPU_01 - 5.83 sec - Booleans and Contours
CPU_02 - 1.17 sec - Twist and Taper (UDT)
CPU_03 - 2.87 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.02 sec - Join Render Mesh
CPU_06 - 10.74 sec - Reduce Mesh
CPU_07 - 0.88 sec - Calculating Technical display
CPU_08 - 2.82 sec - Making Silhouettes

System manufacturer
System Product Name

NVIDIA Quadro P2000 - 4095.0 MB
DriverVersion: 23.21.13.9133

Intel® Core™ i7-8700 CPU @ 3.20GHz
NumberOfCores: 6 NumberOfLogicalProcessors: 12
MaxClockSpeed: 3.19 GHz

TotalPhysicalMemory: 32.0 GB

Microsoft Windows 10 Professionnel

None - 64 bits

Rhino 6 sr 12 64 bit
AA level = 8

Jonish · January 12, 2019, 10:05am

Hey guys, I wonder why I can’t install this on Rhino 6, only on Rhino WIP.
Nevertheless,

Intel i7 8700K, Nvidia GeForce RTX 2070.

Holo · January 13, 2019, 1:12pm

Wow, that is rivaling Jeff’s GV100… Nice!
And quite similar to BauerNavals system with the same CPU and a 1070, but for some reason he gets really fast meshing of the mini and that boggles my mind. HitEnter and Nathans systems get 3.xx seconds on the meshing too, so it seems people are either getting 3 or 7 seconds on the meshing. I’ll investigate a bit. (It almost seems like it uses different mesh settings, but it should not since meshing is a document setting and I use “_-New %filepath%” to make a new file based on the mini document, so all systems should use the same meshing settings…
(I can confirm that that works as it should, and my laptop uses 4.4 sec to mesh when I have 4xAA on (I saw that my initial test on 0x vs 4x AA had different meshing scores) so your system should be faster than 7 seconds)

jeff · January 13, 2019, 6:23pm

Well…we can’t have that now can we… LOL

@Holo I think you can probably increase the granularity of your unit tests… If you bump the unit count up by 10 units instead of 1, you will arrive at the exact same results (or close to it) much, much sooner.

-J

AlW · January 13, 2019, 7:30pm

GV100, Quadro RTX 6000. No wonder Rhino costs so much, just to keep Jeff in video cards. Nathan, too.

jeff · January 13, 2019, 7:31pm

You don’t actually think I pay for these things do you?

AlW · January 13, 2019, 7:33pm

Well, then: I’d like to get to know who you do.

nathanletwory · January 13, 2019, 7:40pm

Too bad I still don’t have any RTX yet ;.;

AlW · January 13, 2019, 7:44pm

Just talk to Jeff. Apparently he knows exactly how to fix you up. Probably just needs your FedEx address.

jeff · January 14, 2019, 10:26pm

Man things sure look better on the Mac in 5K… colors are brighter and more vibrant…albeit slower too…but it just looks awesome… posting a pic here probably doesn’t give it justice unless you’re viewing it on a 5K monitor or a Mac. I’ve seen other 5K monitors though, but none look as good as the one on my iMac.

Just messing around with Jorgen’s model testing some things on the Mac, thought I’d post it here in this thread.
-J

Holo · January 14, 2019, 11:18pm

Nice! I’m glad to see that the model do justice to that kind of resolutions too (even though it could benefit from a bit more details though)
Really cool to see that the Mac version is going to deliver great real-time graphics too!

FPU · January 15, 2019, 4:54pm

@Holo Looking at the posted scores, i noticed that every GPU with 4GB VRAM or more is presented as having 4095MB VRAM. Is there something wrong?

jeff · January 15, 2019, 5:14pm

Yes and no, Jorgen is probably just not getting the right value…there are two values that drivers store, a 32bit version and a 64bit version…if there is over 4GB, then the 32bit version will always be 4GB… so either the wrong value is being asked for, or the value being returned is getting stored into 32bit integer instead of a 64bit long integer.

It doesn’t mean anything is wrong with your system or Rhino…if you go into Rhino’s OpenGL settings page, you should see the correct amount being reported.

-J

FPU · January 15, 2019, 6:37pm

Pretty plausible explanation. Thx!

Slightly offtopic question: Quadro cards were a no-brainer for Rhino 5, because Quadro-drivers are optimized for OpenGL. How does Rhino 6 run on GeForce cards?

Holo · January 15, 2019, 8:36pm

Ah, thanks for chiming in Jeff! Yes, I’m quite sure I’m asking for the wrong value and that was never an issue in the beginning of Holomark2 since no cards had more than 4GB
I’ll see what I can do to correct this.

Oh, and Rhino 6 seems to run as smooth on GeForce cards as Quadro cards so far.

Architex · January 16, 2019, 12:12pm

All macs use a LG screen panel. Their not from APPLE fabric.

bwheeler · January 16, 2019, 1:51pm

Here are the scores from my 2 systems I use…Desktop gets used daily and the laptop only at home or at job sites. The laptop is only about a year old and scored much higher than the 5 year old desktop, that said the laptop doesn’t really seem that much faster than the desktop. I did just replace the graphics card in the desktop with a 1050 card.

Desktop…
Holomark 2 R6 v2,61

Total Score: 69501
Total Runtime: 265.43 sec

GPU scores: 56450
GPU_01 - 381.00 fps - Cube 4 tests
GPU_02 - 51.00 fps - UDT Shape
GPU_03 - 163.90 fps - Wireframe
GPU_04 - 156.30 fps - Shaded
GPU_05 - 94.30 fps - Rendered
GPU_06 - 119.00 fps - Block Rendered
GPU_07 - 73 units Nurbs @ 5 fps in Wireframe
GPU_08 - 64 units Nurbs @ 5 fps in Shaded
GPU_09 - 124 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 125.00 fps - RenderMesh Render
GPU_11 - 303.00 fps - RenderMesh RenderSpeed
GPU_12 - 263.20 fps - JoinedMesh Render
GPU_13 - 526.30 fps - JoinedMesh RenderSpeed
GPU_14 - 40 units mesh @ 15 fps in Shaded
GPU_15 - 55 units mesh @ 15 fps in Render
GPU_16 - 167 units mesh @ 15 fps in RenderSpeed
GPU_17 - 128.20 fps - mesh in Rendered Studio
GPU_18 - 43.30 fps - Nurbs in Rendered Studio
GPU_19 - 50.80 fps - Block Illustration
GPU_20 - 71.90 fps - 2D single
GPU_21 - 34.50 fps - 2D massive (20x)

CPU scores: 13051
CPU_01 - 8.04 sec - Booleans and Contours
CPU_02 - 1.66 sec - Twist and Taper (UDT)
CPU_03 - 3.83 sec - Meshing Mini
CPU_04 - 0.04 sec - Extract Render Mesh
CPU_05 - 0.03 sec - Join Render Mesh
CPU_06 - 19.09 sec - Reduce Mesh
CPU_07 - 1.84 sec - Calculating Technical display
CPU_08 - 3.78 sec - Making Silhouettes

ASUSTeK COMPUTER INC.
M51AC

NVIDIA GeForce GTX 1050 Ti - 4095.0 MB
DriverVersion: 24.21.13.9907

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

TotalPhysicalMemory: 16.0 GB

Microsoft Windows 10 Pro

None - 64-bit

Rhino 6 sr 12 64 bit
AA level = 4

Laptop…
Holomark 2 R6 v2,61

Total Score: 181227
Total Runtime: 855.25 sec

GPU scores: 168210
GPU_01 - 123.80 fps - Cube 4 tests
GPU_02 - 56.20 fps - UDT Shape
GPU_03 - 357.10 fps - Wireframe
GPU_04 - 303.00 fps - Shaded
GPU_05 - 103.10 fps - Rendered
GPU_06 - 137.00 fps - Block Rendered
GPU_07 - 612 units Nurbs @ 5 fps in Wireframe
GPU_08 - 415 units Nurbs @ 5 fps in Shaded
GPU_09 - 91 units Nurbs @ 5 fps in RenderSpeed
GPU_10 - 138.90 fps - RenderMesh Render
GPU_11 - 294.10 fps - RenderMesh RenderSpeed
GPU_12 - 357.10 fps - JoinedMesh Render
GPU_13 - 588.20 fps - JoinedMesh RenderSpeed
GPU_14 - 122 units mesh @ 15 fps in Shaded
GPU_15 - 247 units mesh @ 15 fps in Render
GPU_16 - 969 units mesh @ 15 fps in RenderSpeed
GPU_17 - 204.10 fps - mesh in Rendered Studio
GPU_18 - 39.10 fps - Nurbs in Rendered Studio
GPU_19 - 46.30 fps - Block Illustration
GPU_20 - 133.20 fps - 2D single
GPU_21 - 84.00 fps - 2D massive (20x)

CPU scores: 13017
CPU_01 - 7.90 sec - Booleans and Contours
CPU_02 - 1.45 sec - Twist and Taper (UDT)
CPU_03 - 10.62 sec - Meshing Mini
CPU_04 - 0.03 sec - Extract Render Mesh
CPU_05 - 0.03 sec - Join Render Mesh
CPU_06 - 12.85 sec - Reduce Mesh
CPU_07 - 1.18 sec - Calculating Technical display
CPU_08 - 4.35 sec - Making Silhouettes

ASUSTeK COMPUTER INC.
GL702VI

NVIDIA GeForce GTX 1080 - 4095.0 MB
DriverVersion: 24.21.13.9924

Intel® Core™ i7-7700HQ CPU @ 2.80GHz
NumberOfCores: 4 NumberOfLogicalProcessors: 8
MaxClockSpeed: 2.81 GHz

TotalPhysicalMemory: 32.0 GB

Microsoft Windows 10 Home

None - 64-bit

Rhino 6 sr 12 64 bit
AA level = 4

Brian