Years ago I noticed that saving the Rhino files on an SSD is not faster, but I thought that it may be related to the small file size. However, now that I have a 2,4 GB large file that takes way too long to save on my HDD, I decided to move it to my system drive (SATA 3 SSD Samsung 860 Evo), but Rhino is still too slow when it comes to saving. I measured nearly identical times for saving exactly the same file, both, on my HDD and my SSD. I wonder, if the CPU (Intel Core-i5 4460) causes the bottleneck, rather than the type of drive where the Rhino file is being stored? I also use 16 GB (4x4) DDR3 memory.
In Options>Advanced, turn off file compression when saving.
1 Like
Does that mean that the file size will increase when compression is turned off? Also, is the CPU used to compress the saved file? If so, looks like a new CPU with plenty of cores will help a lot? 
Edit: I just did a test with the file in question, and your suggestion helped to cut the file saving time more than twice at the expense of some extra storage space. Thanks a lot!
Compession on: 75 seconds to save, file size is 2409 MB.
Compression off: 30 seconds to save, file size is 2724 MB.
Your CPU is from 2014. The everything is the bottleneck. You should have like 128GB RAM for working on 2GB+ files, how much virtual memory are you using?
It’s set to “System managed size” and is currently 2935 MB. The memory utilization of Rhino 7 while I work on that particular file is never above 9 GB RAM. Performance is great, it’s the slow saving and autosaving that takes a huge time despite using an SSD.
Hi Bobi, when you say “ a huge amount of time”, is that 10 minutes?—-Mark
No, I mean more than a minute. As I mentioned in an earlier post, saving to my SSD with compression turned off takes whole 75 seconds for a 2,4 GB file. Saving the same file on my HDD takes 81 seconds, which is a negligible difference, considering that my SSD should be approximately 4-6 times faster.