We occasionally get reports that saving a Rhino file saving to a network disk is much slower than saving to the computer Rhino is running on. We have been unable to reproduce this problem using our own networks and using various cloud storage services.

This information might help your IT department tune your server settings.

• Some customers have found encyption to cause slow network saves.
• Some of our customers have had success disabling VMQ. https://discourse.mcneel.com/t/rhino-6-slow-save-to-network-location/79177/14
• This Discourse post gives a list of some other things to try. https://discourse.mcneel.com/t/rhino-6-slow-save-to-network-location/79177/13
• By default, Rhino saves files by using fwrite() to send 64KB chunks to disk. When a file contains large objects (big meshes, big polysurfaces, …) there is a “seek” operation for each large object. You can use the SetArchiveMemoryBufferSize command to change the default chunk size and reduce seeks. As a first attempt, change 64 to 32000 and try saving. If that helps, then it's possible that your server has a high overhead per write transaction. If that doesn't help, set the size back to 64.

If none of this helps, please use Discourse or contact technical support and include this information:

1. The information from Rhino main menu > Help > System information.
2. Local computer virus checking software.
3. Network server OS.
4. Network server file system information.
5. Network server virus checking software.
6. Any special network settings you are using (encryption, compression, time outs, …)
7. Find a Rhino 3dm file that saves fast locally and saves slowly to a network disk. Determine the size of that file and create a Rhino file of the same size containing only lines (use array to make thousands of lines from one). See if the lines file also saves slowly. (Saving the lines file sends thousands of small chunks to the server with very few seek operations. Knowing the results of the lines test helps us to either focus on or rule out network seek speed.)