Vault Client Slow over network

[hellms]

When using Vault Client with a working directory on the network, it takes a few seconds for any operation. The user interface is very sluggish and pauses every so often. There are about 544 files in the project. There are some constraints about this project that force us to keep it on a network drive. Making the working directory local makes things responsive again, but this isn't a good solution for us.

Client Information
Vault Client Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 3 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)

[lbauer]

Vault was designed with the assumption working folders would be on the same machine. You can have working folders on a network drive, but if the client has network overhead each time it has to scan the contents of the working folder, apply deltas, etc. this can reduce performance.

One thing you could try is to set working folders only for the repository folders you are using at a particular time. This might reduce the amount of comparison that needs to be done of working folder against repository folder.