How to improve Vault Server performance?

[Tri]

Besides the DB maintenance and repositories organization,
Can you please advise about the settings to improve Vault server (2.06) performance. And what are the factors which are most likely to reduce performance?

Some of our users (within the same LAN than the Vault server) reported 'could not connect' issues. Could it be due to some other users making some large 'Get Latest?

[lbauer]

Probably the best way to improve Vault 2.0.6 performance is to upgrade to Vault 3.0.1

Since you're posting to the Gold Support forum, I assume you have Gold Support, which entitles you to a free upgrade.

For upgrade information, see:

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

And for new features in Vault 3.0, see:

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

[Tri]

Yes, we qualify for 3.01 upgrade. Is the 2.06 -> 3.01 a seamless upgrade? For the customers who already made the migration, can you share some experiences on what need to be taken care of particularily?

Even with 3.x my question above still prevails. How to better maintain the server and what are the factors which impact the performance.

[kadorken]

The upgrade went without any problems whatsoever. The only 'change' we have noticed is a occasional request to 'login' to the vault server and pick a repository after a session has timed out overnight.

[lbauer]

To answer Tri:

Performance can be affected by many things.

-- fragmentation of the drive where Vault database resides
-- inadequate disk space or system resources on machines running Vault and the database
-- a large number of files (1000+) checked out at any given time
-- a concurrent usage by many users, though this has been improved in Vault 3.0
-- recycling of IIS sessions in Win 2003

Perhaps my colleagues will chime in with some other factors.