The Help Page about Computation Analytics does not explain what the “collect” time corresponds to. Is there a reference/documentation to what part of the process this refers to?
Thank you!
The Help Page about Computation Analytics does not explain what the “collect” time corresponds to. Is there a reference/documentation to what part of the process this refers to?
Thank you!
If you mean time_solver_collect, this represents the time it takes the server to prepare the data to be sent, after the actual computation in Grasshopper returned a result. This is typically a small amount of time but can increase in case the output data and geometry is spread through multiple outputs or organized using big data tree structures or attribute schemes.
If you are experiencing long collect times, feel free to share a minimal example showing what type of outputs your definition produces.
Generally there are no data trees, everything is flattened in my case.
I was just curios as I had a one-off where I got 20s collect time but generally it is below 1s. I did have 2 different Shapediver Output components. Is it a best practice to always bundle everything into just one output component? Thanks @mathieu1