My office is experiencing very slow file open and file save operations when opening or saving files to our office server. Opening or saving the same file locally to our workstations takes a fraction of the time. 9 second file save to local vs 9+ minute file save to server.
I have read through the numerous other threads on the forum describing similar issues and have tried a variety of solutions but nothing has helped. (Change SetArchiveMemoryBufferSize, Turn off/on file compression, turn on Rhino.Options.FileSettings.WriteLocalTempFileWhenSaving, Disable VMQ on server, etc.)
The above referenced times are for a test file I created that is large but basic. The file is an array of ~260,000 spheres (no materials) that creates a roughly 727mb file. This is of course a very large file but the problem is also present on actual project files that are much smaller, say 150mb. Our office has regularly worked with Rhino files in the 500mb to 1.5Gb file size for years and have not had significant issues. I am not certain exactly when the issue began for us but I think it was around the time we upgraded our server (a few months back). Having replaced a 10+ year old server, the new server should be better in every way at least in terms of performance specs. But I suspect there is perhaps some issue between Rhino and our server. If I copy the same Rhino file directly to the server the file is transferred almost instantaneously.
A little bit of additional info about the behavior that I have not specifically seen described in the other related threads. When I hit save and immediately check the network activity in task manager, I see a spike in send network activity peaking at roughly 950mb/s. That holds steady for about 10 seconds or so and then send activity drops to 0 mb/s and then occasionally fluctuates up to ~40 mb/s before dropping back to 0 mb/s and then repeats but mainly staying at 0 mb/s. After the first 15 seconds the file appears to have been completely saved, at least in terms of file size seen on the server. The file size on the server at that point is the final file size but back in Rhino the save operation is still ongoing. I cant help but think that first 15 seconds is the actual time it is taking to save the file and then something else is happening. In this example, the save operation continues for another ~9 minutes with seemingly nothing happening(or I should say I just don’t know what is happening). Then after 9 minutes the save completes in Rhino, but the file time for the newly saved file on the server does not change from the time the file was created 9 minutes prior. Perhaps this is normal activity, but I just wonder what is happening in that long period after the file has been created on the server and Rhino completes the save operation.
Any help would be much appreciated, this is really killing our workflow.
If you take one of the files that you copied to your PC and use file manager to rename it to test[something].3dm and, again in file manager, copy it to the folder on the server where you normally save your Rhino files does that take about as long as saving it from Rhino or is it pretty instantaneous?
Hi Wim. OK, tried changing the WriteLocalTempFileWhenSaving, here are my results. I did notice unique behavior in each condition. FYI, I made a smaller test file so numbers wont match times in first post.
WriteLocalTempFileWhenSaving = True
Save time (two tests) = 3m30s / 3m38s
When setting is set to True, the behavior is consistent with what I described in my original post. Short period of high network activity (950mb/s) followed by long period of minimal network activity (fluctuation between 0 mb/s and 40 mb/s) for remaining minutes. File size on server is full size within 10 seconds of save.
WriteLocalTempFileWhenSaving = False
Save time = (two tests) = 4m30s / 3m50s
When setting is set to False, the behavior is slightly different. Consistent ~50mb/s for the first minute of file save before file reaches full size on server. A temp file is visible while this is happening. Followed by 3 minutes where behavior is the same as above (fluctuation between 0 mb/s and 40 mb/s).
Let me know what you make of it.
The setting does appear to make a difference, but file saves to server are still orders of magnitude longer than local drive saves.
Yea, the issue was present prior to this release, I had just not had time to report issue. Is the behavior I describe in my previous post normal? Hoping for some help, this is really slowing down our workflow. And we dont know what to tell our IT company as other programs/tests dont show the same issue. Not sure what mix is causing the issue.
No, not at all. That’s not something that we’ve seen before and only has people scratching their heads around here.
I suppose we could try to eliminate (or not) Rhino from the picture by at least going back to a Rhino version that you were running before the server upgrade. That Rhino version worked fine for you at that point - if that same Rhino version no longer works fine now, it sounds like it a server thing. If that same Rhino version still works fine, we’ll have to try to narrow down which exact version of Rhino went wrong in your environment. Or?
How often do you update the Rhino version, and when was the server upgraded?