I would like to get some further details on the Support Files and the bloating which some companies get, which in turns creates a very slow load/save process.
There definitely seems to be a direct correllation here because when then the Support Files size goes back down, the performance increases dramatically until the next bloat 'cycle'.
My understanding of this is that this happens due to incomplete saves on the network so therefore RS is keeping a log of changes until the next full save can be achived, after which it can then dump the suport files.
I have a very specific question to ask if the latency on the network between office locations would be a very likely contributor to this? Autodesk's own literature recommend a latency of <100ms.
I have seen some companies who are having Support File bloat issues, that also have an office on the RS network who have latencies of 300-400ms. i.e. Up to 4 times the maximum recommended.
Is there a correllation here too?
I'm hoping to get some comments from both users (who have tested/experienced this), and Autodesk with their technical knowledge.
Solved! Go to Solution.
Yes, the latency could be related to the support file sizes. When Revit goes to save changes to a central model it uploads the data in a temporary area and only makes the model changes if all of the data has been confirmed to arrive at the server in tact. So if a sync fails to complete, the data gets uploaded but no changes get committed. An increase of the support file size is symptomatic of operations that are failing to complete and often a problem with network performance or reliability.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register