Major lagging in Rhino caused by clusters in disabled Grasshopper script

Rhino
,
1

We have a serious lagging issue in the script that contain many clusters.

The issue setup:
Rhino is set to shaded, rendered or any other view than wireframe
A grasshopper file containing many clusters is opened (even with solver locked)

The issue:
The mere selection of curves in Rhino is extremely slow. It causes serious lagging with several seconds of waiting.

What we’ve tried.
We have been through and set all objects inside clusters to preview off.
We see an increase in lag the more clusters we place. Exploding the clusters removes the lag.
We come from Rhino 7 where this was no problem - we have tested in Rhino WIP where this is also no problem. However, in Rhino 8 this is a massive issue for all users of our tool.
We upgraded to Rhino 8 a while, but this is forcing us to downgrade the entire company (not mine, a client’s) back to Rhino 7.

The current only solution:
Exploding all clusters… which is very much against our philosophy of keeping repeating code maintainable.
Downgrading to Rhino 7 - We are already relying on many of the new native features in GH in Rhino 8.
Upgrading to Rhino WIP… Not ideal

Wish:
Is this possible to get fixed in a Service Release :grimacing:

Attached files
A file containing a series of polylines similar to that of a project file.
Clean Polyline File.3dm (4.7 MB)

Two gh file, one containing clusters and another similar file with no clusters.
Clusters.gh (453.2 KB)
NoClusters.gh (749.3 KB)

How to replicate:
Open the rhino file, set to shaded view, open grasshopper, lock solver, open clusters.gh. select objects in Rhino

3

Thanks I’ll take a look. Its similar to this report that i haven’t been able to repeat. I’ve assigned this to Kike for the moment.

4

I don’t think cluster is the issue, I think the loading of Python & C# into Rhino is. Cluster amplifies it to a significant level. Look at the screen recording below where the first instance of Python and C# components take quite a lot of time while the subsequent ones are almost instant. It wasn’t an issue with Rhino 7 though.

Unlike OP we don’t have the luxury to roll back to Rhino 7 so could you please put this higher on the list?

Even if you could somehow make the loading of Python and C# part of Rhino startup for now that’d feel much better for our end users because otherwise having a frozen GH script for 1-2 minutes after clicking open is not fun.