ShapeDiver - Comp. time

Grasshopper ShapeDiver
1

Hi @mathieu1

Since last Friday, one of my client’s models has encountered issues related to computational time. Before that, the model was performing well, often nearing the 10,000 ms limit when exporting PDFs, but it was always successful.

However, starting last Friday, the model began experiencing problems that exceeded the computational time limit when exporting. We are currently working on a new version of the Grasshopper file to enhance computational performance. It’s peculiar that the model never had these issues prior to last Friday.

image
image1920×924 226 KB

Has there been any recent changes on your end that might be causing this problem? Please let me know if there is anything we can do in the meantime while we prepare the improved version.

I’ve attempted to clear the cache, but it freezes when working with Outputs.

image
image1920×924 170 KB

2

Computation times in Rhino in general and on servers vary depending on various factors. It seems that your definition is computing on average in around 10 seconds, and it is likely that it then frequently exceeds the limitation on your account. Optimizing the definition is a good way forward, feel free to ask for advice here or check our resources about this topic. Also consider upgrading to longer computation times if needed.