Rhino file extremely laggy even on a high end PC

My project is extremely laggy on both a MacBook Air and a Windows PC with a high ends graphics card. Adjusting the slider immediately freezes the project and slows everything down. I’m not sure what is wrong. Could someone help me with this? I would be so thankful if you could help me resolve this problem.
Assignment3.gh (18.1 KB)

Hello - what slider?

Can you please run the SystemInfo command in Rhino and copy/paste the results here?


Thank u so much for replying. You don’t know how much I appreciate that.
Any edits just slows down the project. My friend who’s testing it on Mac has the spinning wheel of death and I just take forever to load after any minor edit (like adjusting the number slider on Grasshopper)
systeminfo.txt (2.1 KB)
Rhino 7 SR4 2021-3-19 (Rhino 7, 7.4.21078.01001, Git hash:master @ a432d22ab7f0f7b53d157d578278070c8bf6eff4)
License type: Evaluation, build 2021-03-19
License details: Stand-Alone
Expires on: 2021-07-08

Windows 10.0.19041 SR0.0 or greater (Physical RAM: 32Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3090 (NVidia) Memory: 24GB, Driver date: 3-25-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 465.89
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0

OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On

Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High

Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-25-2021
Driver Version:
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 24 GB

Rhino plugins that do not ship with Rhino

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\IronPython\RhinoDLR_Python.rhp “IronPython” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\Grasshopper\GrasshopperPlugin.rhp “Grasshopper” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”

Hi Oscar - Can you describe the symptoms more precisely? What exactly is slow - selection? Some specific operations? If so which? - (I am thinking of Hide and Undo in particular)
You might try getting the latest Service release - I am not certain that will help but it might - there were a couple of ugly slow-down bugs that are fixed but I think in 7.6 at the soonest.


I guess the question is what do you expect? Grasshopper is a programming tool–and one that’s more optimized for ‘ease of use’ than ‘performance’—through which you can easily make situations that will bring any machine to its knees, as it all comes down to single-core performance, trying to make code that actually makes use of multiple cores or CUDA takes a lot of work and is often theoretically impossible. I don’t know why you think the video card makes any difference. I tried it out and…yeah it’s not instant but it’s faster than doing it by hand, that’s the whole point. Do you really expect it to be as fast as if it’s something in a game? It’s not the same thing, kids.

Here’s an alternate route to take to optimize the script, maybe you will find it helpful.

Assignment3-djedit.gh (20.1 KB)

FYI, the Gh pipe component is pretty slow except on very simple curves. You can try mesh pipe (in addition to what I showed above in the script I posted) if you are just rendering, it is a lot faster.

1 Like

Oh my god. It’s actually much faster now. Like noticeably faster. Adjusting the slider is pretty smooth now… Thanks so much Devin. Can you explain what u did to achieve this?

I rebuilt the catenary curves (which are curves made up of a bunch of little straight line segments, making it a degree 1 curve) with their control points so that they are smooth degree 3 curves with the same control points. From my experience, piping a degree 1 curve with a lot of little segments is a lot slower than piping the same curve rebuilt as a smooth degree 3 curve with the same control points.

[edit] the rebuild doesn’t use the exact same points, but uses the same number of points, you could also rebuild with the exact points using interpolate curve.

I highlighted the nodes that I added in the picture below:

1 Like

Difference between Nurbs Pipe and Mesh Pipe för the same curves:

// Rolf


If ONLY replacing the Pipe components to Mesh Pipe, there’s almost no noticable lag when dragging the dividing Slider between 0 … 100.

Its around 35ms for 30 divisions, and about 120ms for 100 divisions.

1 Like

I think it is obvious that the problem has been made because of the pipe component(specially second one), so basically , I think by flattening the output of catenary component you can increase the algorithm speed :slight_smile: