I have noticed some odd behaviour with Rhino 6. I am working on some large projects and the save time is extremely long (20 minutes for some of the files).
The project I am working on has a series of setups starting small and scaling up- I’ve been monitoring the disk usage when saving and noticed that the write rate of saves scales down proportionally to the file size. The smaller files (roughly 300 mb) save very quickly with a decent write rate of ~40 Mb/sec. However this drops as the files get bigger, exacerbating the time increase from the larger file. 1gb files appear to be limited to roughly 15 Mb/ Sec, by the time the project reaches the 2gb file size this drops to just 3Mb/ sec resulting in a roughly 11 minute wait every time I save the project.
There appears to be a bottleneck in how Rhino handles saves- when saving the cpu is pegged at 20% usage (the machine I am using is a 7th Gen i7 with 8 threads so looks like it’s limited by single core performance?).
Edit: A side note- the other thing that occurs to me, the files in question are comprised of many copies of the same set of objects, evidently Rhino treats these as independent. It’s a shame the software can’t recognise the identical copies of the same objects when saving as this would reduce the file size substantially…