Hi, I am using the new speckle connector for Rhino/Grasshopper (v 3.3.0) and in one use case I have created more than 11000 objects in less than a minute. See image below. In this case, the objects are Breps (simple extrusions) and 23 properties per object.
In another similar use case, I am trying to create ca. 6000 objects with very similar characteristics (Breps as extrusions and 17 properties per object) but in this second use case it is taking 30 minutes, which theoretically should be faster. See image below.
Hi @GabrielGarcia , could you let me know which types of properties (strings, bools, etc) and which types of objects (speckle objects vs geometry) you’re using in both cases?
In general, there are two paths for this passthrough component:
mutating existing objects: this happens when you pass in speckle objects into the objects input
creating new objects: this happens when you pass in geometry objects into the objects input
The two actions may have different performance implications, but without more details it’s hard to say if it’s the geometry, the properties, or the method that is the culprit for slow solving.
The easiest way for us to debug this is if you could send over a simplified script with the objects and properties, and I can look into this locally to see what’s causing the slowdown
Hi @clrkng, in both cases, I am creating new objects passing the Brep geometries (simple extrusions). The properties are text, integers and decimal numbers.
The weird thing is that both cases are very very similar. Even the geometries are more complex in the fast use case.
