Vault 4.1.x Performance

[stegess]

I'm currently running Vault 4.1.1. I've read many posts regarding performance and the various settings in Vault. The primary performance problem we continue to experience is when the Client is first launched and is "Retrieving respository information from the server" -- this can sometimes take up to 1 minute to complete (and that's good, compared to what I've seen reported by other users) -- still it's a serious impact to productivity.

Can you summarize, in a very concise manner, the current best practices for optimizing the service? Please discuss every Vault setting that affects performance related to the above problem, starting with the settings that have the most dramatic impact in most situations.

I've watched the server processor loading and memory usage when clients connect, and I barely see any change-- so I don't think the server is overburdened by the task of sending the repository to the client.

[lbauer]

The first thing we would recommend it to upgrade to Vault 4.1.4. That way you'll take advantage of any performance improvements in the latest version. In addition, if we troubleshoot further, it's best to be in the latest version.

Next, review the suggestions in this forum post:

http://support.sourcegear.com/viewtopic.php?t=4206

If you continue to find issues with performance, e-mail support at sourcegear.com, Attn: Linda. Please include a link to this forum post, and we will look into any bottlenecks you may be experiencing.