How to Optimize Computation Time on Website with ShapeDriver for a Grasshopper Model?
I have created a lean Grasshopper model and uploaded it to ShapeDriver for use on my website. However, I noticed that the computation time increased by 2-5 seconds after adding a mesh geometry (Dummy) with around 8000 vertices and meshes that I’m moving 500 to 600 mm based on the product size. Is this normal? Are there any optimization techniques to decrease the computation time? Can anyone explain why this is happening? Can it be because of any display option in shapedriver?
The size of the geometry in your definition has an impact on the overall performance of your application in your web browser because the geometry needs to be downloaded every time it is updated. However, 8000 vertices is not such a significant mesh and should not impact the performance so much. It depends on what you mean by “adding a mesh geometry”: using the import component, displaying external glTF, internalizing geometry in Grashopper, etc…
Thank you for your response. When I said ‘adding a mesh geometry’, I meant that I imported a single mesh geometry into Rhino and internalizing geometry in to a Mesh component of grasshopper. This geometry is now being moved left or right as I adjust the length of the product (shown in green).
