Hello all, Ive seen this raised on other forums but sadly to no avail, and so i thought id try my luck here. When creating a definition, I have noticed that the runtime of the definition differs significantly if you cluster it. Ive investigated this for a few days now and have come to the followin…

I’ve encountered this issue before, and it’s frustrating not being able to selectively expire components in a cluster, especially when it involves continuously-running things like Kangaroo solvers One easy workaround is to use a DataDam directly after the cluster inputs which cause expensive operat…

Hello qythium, ive tried the data dam route, but it didnt solve my problem in anyway, if you have a quick read to the update of my post above, i believe the issue seems to be with the translation of data from outside the cluster to inside the cluster… When i put the data dam directly after the ‘clu…

Are your input parameters themselves very large or composed of many items? I believe there is copying of params going on at the cluster interfaces which may cause delays for heavy inputs- maybe you could provide a sample gh file

The input paramaters are quite large yes… however, when doing my tests… when my two data sets were inputted as two separate inputs into the cluster, the cluster was 4.7 seconds… however, when i ‘Entwined’ the two data sets outside of the cluster so that both sets are within one list… and i input the…

I’ve logged this under RH-44500 . I’m not sure the problem is fixable in Grasshopper 1.0, it will require a lot of performance counting first.

I just committed some changes to the way clusters deal with expiring inputs in the current Rhino7 WIP code. So hopefully when the next weekly version is released clusters will work faster if they can re-use large swaths of the previous solution. And even more hopefully the testing I’ve done didn’t f…

Thank you! This will make the clusters much more of a feature to use. I had a design last week where I wound up copying chunks of code, as i did not want to go the cluster route. Next week i will use the new version.

Cluster runtime very slow

Grasshopper

brian (Brian Gillespie) April 28, 2020, 10:50pm 8

RH-44500 is fixed in the latest WIP

Wish: Only recalculate downstream inside clusters

Topic		Replies	Views
Wish: Only recalculate downstream inside clusters Grasshopper	5	1265	June 12, 2020
Clusters do not Recalculate in Rhino7 Grasshopper	36	4667	November 26, 2024
Impact of clusters on performance Grasshopper windows	6	608	April 15, 2024
Cluster compute logic issue (Rhino 7.20) Grasshopper windows , cluster , rhino7	0	448	August 22, 2022
Confusion over solution and output logic of the cluster？ Grasshopper Developer	3	471	March 15, 2021

Cluster runtime very slow

Related topics