SourceGear Support

We have several customers where our call to ServerOperations.Login() more than a minute to complete. Is there any way to improve on this?

Eric

Hey Eric,

I see two significant gaps The first is 46 seconds to load the CacheMember_Repository file. How big is that file?

There's also a 15s gap where it's cloning the full repository.

I think that the slowdown is a symptom of a really big repository. Does that match what your customer is saying about their Vault repository?

The slow performance is continuing to be a problem for a number of our customers. Several are resigned to it, however, a couple customers are continuing to have problems with it, as making the connection takes several minutes. One of these customers reports their CacheMember_Repository file is 17MB. Is the problem with the performance of reading/writing this file? Is there anything you can do for them?

In my experience, most customers who are reporting a long time to load the repository are benefited by reducing the number of nodes (folders and files) in their repository.

The best way to do that is to load up the NodeCounter power toy (from http://www.sourcegear.com/vault/vaultpowertoys.html) and look at the distribution of nodes in the tree. Figure out which nodes are no longer necessary, and delete them. It is not necessary to obliterate them to see a speed increase. Just delete them. If you ever need those folders again, you can undelete them.

For example, you can delete old branches that have been merged into trunk, as well as any old releases that we would no longer change, even if there was a bug.

Has this problem been solved with newer versions of SourceGear, or is the login performance slow on these many node repositories. Our standard login takes about 20-40 seconds, and we do it often... major user complaint.

One of the things we found that speed up logins is turning off the option "Request Database Delta on Repository Cache Miss." This is in the Vault - Tools - Options - Concurrent Development Style

Other things that help are:

-- Work in VSS mode instead of CVS mode (causes extra scanning)
-- Don't turn on Ghosted files and folders (causes extra scanning)
-- Change the auto-update statistics setting per this KB article: http://support.sourcegear.com/viewtopic ... 13&t=22358
-- SQL Maintenance: http://support.sourcegear.com/viewtopic.php?t=2924

There are more things one can look at, but these are the main ones that affect an initial login.