Revit performance problems over WAN
Hello Experts - I'm relatively new to supporting architects and could use some advice on how to handle a performance issue with Revit 2014. Users have been complaining that working on Revit models between offices on a 10mb MPLS WAN is slow to the point of being difficult to use. We have a fairly large model (188mb) that came up as an issue this morning. It takes upwards of 25 minutes for it to sync across the WAN and during this time no one can make changes. With three users working on the model the synchronizations are taking longer than the work done in some cases.
I'm not really sure where to start with this one. The users have capable Dell Precision workstations, not the fastest but they should be up to the task. The file server (2003) is virtual and runs on VMware Vcenter 5.1. The storage system is a new Netapp 2240. Everything is connected with gigabit HP switches and the WAN between offices are both 10mb MPLS circuits.
One recommendation I've been told may help is to install a Revit 2014 server but I don't know much about it. I would appreciate any feedback or advice on the topic, thanks!
I'm not really sure where to start with this one. The users have capable Dell Precision workstations, not the fastest but they should be up to the task. The file server (2003) is virtual and runs on VMware Vcenter 5.1. The storage system is a new Netapp 2240. Everything is connected with gigabit HP switches and the WAN between offices are both 10mb MPLS circuits.
One recommendation I've been told may help is to install a Revit 2014 server but I don't know much about it. I would appreciate any feedback or advice on the topic, thanks!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
No problem. Hope it helps, or at least points you in a direction.
Another thought I had:
Also, you can run a CMD>Tracert (IP Address) to the server from one of the satelitte workstations.
It will show you the "Hops" the data takes to get to destination.
Check the lines for your ISP name and other re-director domains.
If this is stalling somewhere or redirecting to wild places, you may have an issue with your ISP.
I always dislike telling people that an upgrade is the best fix, because it seems like a cop out, but my aged 2003 server really slowed down my network the last year it was up. It had a solid 10 year run, and was functional still when decommissioned.
Another thought I had:
Also, you can run a CMD>Tracert (IP Address) to the server from one of the satelitte workstations.
It will show you the "Hops" the data takes to get to destination.
Check the lines for your ISP name and other re-director domains.
If this is stalling somewhere or redirecting to wild places, you may have an issue with your ISP.
I always dislike telling people that an upgrade is the best fix, because it seems like a cop out, but my aged 2003 server really slowed down my network the last year it was up. It had a solid 10 year run, and was functional still when decommissioned.
ASKER