Very Slow Checkout

If you are having a problem using Vault, post a message here.

Moderator: SourceGear

Post Reply
Greg
Posts: 4
Joined: Sun Nov 07, 2004 6:05 pm

Very Slow Checkout

Post by Greg » Sun Nov 07, 2004 7:44 pm

Vault is a likely candidate to replace our VSS, however, I am experiencing performance degradation when I compare the time taken to checkout an entire project.

In VSS it takes 20secs
In Vault it takes 6 minutes

Should I be concerned?

When I look at the Vault log (debug mode) I see:
  • Getting list of checkout changes.
    GetCheckOutListChanges returned: Success
    Checking out Files
These 3 steps are logged 487 times.

The Vault Server/SQL Server is a 3gig Xeon with a Gig of Ram. The only other application loaded is FogBugz (not yet in use) and there is no Virus checker.

The project contains:

222 files
11 sub-folders
Tree size is 6.7Meg

The FogBugz installation called for database full text indexing to be activated. Would this interfere with the speed of Vault?

Any suggestions around optimisation appreciated...

Greg

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

Post by jeremy_sg » Mon Nov 08, 2004 2:26 pm

That does sound like bad behavior out of Vault. Vault has an API for checking out lots of items at once, but the Visual Studio API may be requesting them one at a time.

I'll try to reproduce this with the Beta version of 3.0.

Greg
Posts: 4
Joined: Sun Nov 07, 2004 6:05 pm

Awesome

Post by Greg » Mon Nov 08, 2004 3:06 pm

Thanks for your assistance.

I'm very keen to eliminate any concerns my development team think they might have and get them across to Vault.

Greg

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

Post by jeremy_sg » Tue Nov 09, 2004 3:34 pm

Greg,

After doing some investigation, it is the Vault IDE client's fault that the items are being checked out one at a time. I would like to try to get this fixed before 3.0 is released, but I can't promise. It may have to wait for a later version. For now, my only recommendation would be to only check out files that you intend to change.

Greg
Posts: 4
Joined: Sun Nov 07, 2004 6:05 pm

...thanks

Post by Greg » Wed Nov 10, 2004 1:31 pm

Awesome, thanks for the prompt response and updates. It certainly makes the decision process easy when I see great service like this.

An early patch would be great if at all possible.

Regards

Greg

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

Post by jeremy_sg » Thu Nov 18, 2004 6:45 am

The fix for this will be included in 3.0, which will be released within a week or so.

Greg
Posts: 4
Joined: Sun Nov 07, 2004 6:05 pm

Great Work!

Post by Greg » Thu Nov 18, 2004 1:15 pm

Awesome response to our requirements.

Thanks Team! :D

Post Reply