Hello,
I’m curious about shapediver’s capacity of holding grasshopper scripts with many different variations of geometry all stored through internalise data. Let’s say I had 50 different versions of a speedboat mesh; how would this effect the loading of the script on the shapediver platform in comparison to 12 versions? Would it be drastically different? For context, the geometry would be relatively detailed.
It is always possible to internalize geometry in your Grasshopper definitions before you upload them to ShapeDiver. In this case, note that the size of your Grasshopper definition will grow with the geometry you internalize, and each ShapeDiver plan comes with file size limitations (see the various limits here).
A very large file will take longer to load initially on the servers, since it needs to be downloaded there before computations can be triggered. For the triggering of computations in itself, this will not have a big influence. In other words, for a configurator which is used frequently, having more or less internalized geometry will not affect the loading of the script too much.
However, you can improve this using external geometry in your definition, in case this geometry just needs to be displayed in the viewer but not process in Grasshopper. In that case, your geometry will travel directly from their storage location to the web browser, without going to the Rhino servers.
In any case (external or internalized), note that the geometry needs to be downloaded to the web browser. If several megabytes have to downloaded every time a parameter changes, the data transfer that needs to happen influences the performance of your application in ways that are unrelated to ShapeDiver itself.