Site Tools


Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
rhino:slow_network_save [2020/10/21]
dalelear
rhino:slow_network_save [2021/02/24]
brian
Line 6: Line 6:
 This information might help your IT department tune your server settings. This information might help your IT department tune your server settings.
  
-   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 objectYou can use theSetArchiveMemoryBufferSize command to change the default chunk size and reduce seeks. As a first attempt, change 64 to 32000 and try saving. If that helpsthen it'likely your server has a high overhead per write transaction. If that doesn't help, set the size back to 64. +  - Some customers have [[https://docs.microsoft.com/en-us/office/troubleshoot/office-suite-issues/saving-file-to-network-server-slow|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 ) +  - Some of our customers have had success [[https://discourse.mcneel.com/t/rhino-6-slow-save-to-network-location/79177/14|disabling VMQ]].   
-  *  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+  - This forum topic gives [[https://discourse.mcneel.com/t/rhino-6-slow-save-to-network-location/79177/13|a list of some other things to try]]. 
 +  - Increase the size of the in-memory buffer used for saving: 
 +    - Run the **SetArchiveMemoryBufferSize** command 
 +    - Set the size to 32000. 
 +    - Try saving again. 
 +    - //Background: 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 data larger than 64 KBIf increasing the size speeds up file saving, it'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
-If none of this helps, please use Discourse or contact technical support and include this information:+Please use [[https://discourse.mcneel.com|Discourse]] or contact [[https://www.rhino3d.com/support|technical support]] and include this information:
  
   - The information from Rhino main menu > Help > System information.   - The information from Rhino main menu > Help > System information.
-  - Network server type and any special network settings you are using+  - Local computer virus checking software. 
-  - List any virus checking software used on the local computer and on the server+  - Network server OS
-  - Find a file that saves fast to a local disk and saves slow 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 lets us either focus on or rule out newtwork seek speed.)+  - Network server file system information. 
 +  - Network server virus checking software. 
 +  - Any special network settings you are using (encryption, compression, time outs, ...) 
 +  - 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.)
  
  
rhino/slow_network_save.txt · Last modified: 2021/02/24 by brian