Vault unusable with working folder on NFS

[illvm]

We're using Vault 3.5 at work and the response time of the vault client makes it completely unusable. I suspect this is due to the working folder being set to a mapped network drive instead of a local drive. I tried using newer versions of the client, but unless the server is updated too I'm afraid I'm stuck with using 3.5. When the client is running I can't even access the options menu. The client just sits there unresponsive most of the time and every so often actually renders a list of files, but even then I can't perform basic source control functions or access any menu items.

I'm fairly certain I won't be able to move the working folder over to a local drive. Any suggestions?

EDIT: Managed to get into the option and disabled automatic refresh. This helped a little bit, but it's still not very usable often taking over 30 seconds to switch folders, get the context menu on a file, etc.

[Beth]

Are other users using the same network folder for their working folder? If so, that can cause some conflicts.

Are any errors showing up in your Vault Server Log?

Would you be able to create a test repository that will be deleted after trying a few things? That is done in the Vault admin tool. Once that is created, connect to it with your client, set a local working folder just for that repository, add some dummy files and see if you can work with them. Is the speed the same or different than it currently is?