ServerOperations.Login() slow

Post your questions regarding using the Vault and Fortress API in your programs.

Moderator: SourceGear

Post Reply
smartbear
Posts: 38
Joined: Thu Jan 24, 2008 10:13 am
Contact:

ServerOperations.Login() slow

Post by smartbear » Wed Jul 29, 2009 12:19 pm

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
Attachments
ccollab_vault.txt
(150.04 KiB) Downloaded 588 times

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: ServerOperations.Login() slow

Post by jeremy_sg » Thu Jul 30, 2009 10:04 am

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?
Subscribe to the Fortress/Vault blog

smartbear
Posts: 38
Joined: Thu Jan 24, 2008 10:13 am
Contact:

Re: ServerOperations.Login() slow

Post by smartbear » Tue Jan 12, 2010 11:55 am

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?

jeremy_sg
Posts: 1821
Joined: Thu Dec 18, 2003 11:39 am
Location: Sourcegear
Contact:

Re: ServerOperations.Login() slow

Post by jeremy_sg » Tue Jan 12, 2010 1:08 pm

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.
Subscribe to the Fortress/Vault blog

RickS
Posts: 3
Joined: Thu Dec 04, 2014 10:09 am

Re: ServerOperations.Login() slow

Post by RickS » Wed Jun 17, 2015 10:27 am

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.

Beth
Posts: 8550
Joined: Wed Jun 21, 2006 8:24 pm
Location: SourceGear
Contact:

Re: ServerOperations.Login() slow

Post by Beth » Wed Jun 17, 2015 3:31 pm

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.
Beth Kieler
SourceGear Technical Support

Post Reply