Hi,
For a data visualization project, we have “slow” loading commits in the web app and we were wondering how big are the commits. We searched all around and couldn’t find a size in Mbs. In order to optimize our data types, It would be nice to know the impact of changes, for example, what is the impact if I change the geometry input from Breps to Meshes in Grasshopper, or properties from text to decimal numbers, etc.
Another advantage may be to uncerstand our digital footprint. Maybe it is wise to delete unuseful big commits to clean up some space in the server.
Thanks!
Understood, though @GabrielGarcia, I should point out that we do not limit your overall storage footprint. The other efficiency we have in Speckle is that, using our newest connectors, you only send what has changed since the last time you pressed Publish.
Could you describe more why you wish to optimise the digital footprint?
Hi @jonathon, thank you for your reply. When I talk about the digital footprint, I mean avoiding storing huge amounts of data in the server when it is not necessary. For example, If every commit is 1GB, I would rather delete all un-necessary commits but now that I understand every commit stores only changes, then my question about the digital footprint is not relevant anymore.
Instead, I still would like to know the size of my models in the server to manage performance. For example, yesterday I was trying to create speckle objects with complex geometries and the “speckle object” component took more than 2 hours to load 842 objects (see image below). This time is directly proportioned with the time to send a commit to the server and I imagine, also the size of the model.
So far, we are blind about performance, maybe we can improve something on our end but we lack of metrics to do so.
