What's the implication or effect on SetArchiveMemoryBufferSize

As a shot in the dark, type the command SetArchiveMemoryBufferSize and enter 32000 .
If that fixes the issues, then the network has high delays for “seeking”. If that doesn’t fix the issue, return the setting to 64 and it is more likely it is a file permissions/locking/renaming/moving or other storage media issue not directly related to sending bytes from Rhino to the storage media.

Hello, I’ve found this fix for an erratic behavior that we were having on a NAS at our office, once we set it to 32K the issue of slow loading of files was gone.

What we’re worried about if there’s any ‘hidden trade-offs’ with this setting enabled, as it’s default value is significantly smaller at 64 instead of 32.000.