Revit over WAN w/ Riverbed

[BMcCallum]

Does Revit resolve the central file location properly when accessing a project through a VPN that is accelerated by Riverbed appliances?

The central file will be stored on a server at one office and accessed by users from that office over the LAN and another office over the WAN. Both offices can map drives to the same share. The VPN tunnel is configured and secure.

[Steve_Stafford]

There are some other threads discussing the use of Riverbed Technology. From what I've seen, read and been told it works quite well when the people setting it up know what they are doing.

[s.messing]

There are some other threads discussing the use of Riverbed Technology. From what I've seen, read and been told it works quite well when the people setting it up know what they are doing.

I cannot take credit for setting up the system, but I can ask for advice now that it is in place. It is most certainly working very successfully in between offices on the east coast, but we seem to be having some trouble with an office on the west coast. The biggest symptom is surprisingly not the STC times, but a simple "Not Responding" message during normal tasks like opening plan views. Sometimes the STC's are slow, are a problem, or cause "Not Responding" message. No matter what the symptoms, I am having trouble pinpointing possible weak links in the system. I have been known to troubleshoot certain issues well, but this one might be over my head. I'd love to hear any advice on what to look for, tests to run, or any "horror stories" that might lead me down the right path...

Thanks,
Stephen

[todd.69291]

Here are some stats from our test of the Riverbed.

Item

Initial copy of 92MB Revit Central File to user Desktop

11 min Ames (Remote)

20 secs Des Moines (Local)

2nd copy of 92 MB Revit Central File to user Desktop

30 sec Ames (Remote)

Moved 1 Door in File then...

Saved to Central File

42 sec Ames (Remote)

20 sec Des Moines (Local)

Reloaded from Central File

62 sec Ames (Remote)

20 se Des Moines (Local)

Rotated 7 tables in file then....

Saved to Central File

1 min 10 secs Ames (Remote)

29 sec Des Moines (Local)

Reloaded from Central File

40 sec Ames (Remote)

25 sec Des Moines (Local)

[Wes Macaulay]

Heh -- not bad times for the WAN! And wait till we start using 2008 -- STC times in my tests are often half of what they were before.