Very slow Vault 3.0.5 performance

bnjsmith · Post by **bnjsmith** » Thu Jan 26, 2006 10:50 am

I recently and suddenly started experiencing very poor Vault performance, e.g., 57 seconds to check out a 600 byte file.
Please see attached VaultGuiClient.txt file. The main culprit seems to be the following action:

1/26/2006 11:33:04 AM <connection>: [GUIClientWorkerThread:3976] GetCheckOutListChanges started.
1/26/2006 11:33:43 AM <connection>: [GUIClientWorkerThread:3976] GetCheckOutListChanges finished.

No other developers - all at the same site - are experiencing a problem, checking out the same file takes 5 seconds or less. The GetCheckOutListChanges for the other developers takes less than 1 second.

The server version is 3.0.5 and I'm likewise using Vault Client 3.0.5.

I've run Error Checking and Defrag on my local drive with no improvement.

I've seen references to the Tools | Options | Local Files | Cache/Backup Locations settings, but I do not have that option. I do have the Local Files option, but not a Cache/Backup Location setting.

Thanks,
Bill Smith

lbauer · Post by **lbauer** » Thu Jan 26, 2006 4:27 pm

No other developers - all at the same site - are experiencing a problem

So the question is -- what's different about your network node, client machine or Vault Client configuration from other users or from your previous state. Has anything changed recently?

If you login from another machine, is the same operation just as slow?

Are you running anti-virus software on the client machine?

I've seen references to the Tools | Options | Local Files | Cache/Backup Locations settings, but I do not have that option.

This was introduced in Vault 3.1. In Vault 3.0.x, the cache files are in %APPDATA%\SourceGear\Vault_1\Client\{repository-guid}\{vaultuser}\

You could try closing your client and deleting the cache file (which will be re-created the next time you log in) to see if that helps.

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

Another place to look for clues is in the Vault server log file to see if any errors are associated with the Checkout.

bnjsmith · Post by **bnjsmith** » Mon Jan 30, 2006 1:35 pm

Hello Linda, thanks for the response. I've narrowed the problem down to my account and a specific repository. IOW, a checkout of 1 small file in repository A took 2 minutes. If I use different login, same machine, again repository A, took 1 second. If I use my login, same machine, repository B, took 1 second.

I am running anti-virus, Symantec AntiVirus Corporate Edition, but all developers are running the same version. In addition, I was running the same version before this problem started.

I tried deleting the cache file, no help.

One correction from my original post: this problem is affecting myself and 2 other developers, not just myself as originally stated. That is from a staff of approx. 30 developers. We are all at the same site.

You asked if anything had changed since the problem started, not exactly, but it began 2 weeks ago after there was a server side Vault/SQL Server problem that was corrected with a reboot. Not sure what the server side problem was exactly as I'm not the Vault admin. After the reboot, all of the users were fine, including myself temporarily. The next day this new problem started and has been pretty consistently present, including the last one week solid.

Attached is a server log for today, I've included the entire log. However the checkout operation that took 2 minutes which was for a single file starts at 1/30/2006 1:51:00 PM and ends at 1/30/2006 1:52:58 PM for the user "bill.smith".

One last note: I do not have any sgbak folders on my machine, even though the "Save files in backup folder" option is checked.

Thanks.

bnjsmith · Post by **bnjsmith** » Mon Jan 30, 2006 1:48 pm

...with attachment.

lbauer · Post by **lbauer** » Mon Jan 30, 2006 5:22 pm

I see the slow checkout, but no errors in the log.

It's possible that there are still network or other issues that are causing the slowdown.

Or, you may just be running into concurrency issues that existed in Vault prior to version 3.0.7.

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

I would recommend that you upgrade Vault. Some versions prior to Vault 3.0.7 were susceptible to a race condition which caused database inconsistencies. They can be fixed, but it involves examining your database in-house at SourceGear.

If you haven't run into it yet, you want to avoid it by upgrading. Vault 3.1.7 is a free upgrade from any 3.x version.

http://support.sourcegear.com/viewtopic ... 1794#21794

bnjsmith · Post by **bnjsmith** » Mon Jan 30, 2006 8:46 pm

If there are database inconsistencies in our database, will the version upgrade fix them, or if they exist will they need to be fixed in addition to the version upgrade?

Thanks,
Bill

lbauer · Post by **lbauer** » Mon Jan 30, 2006 9:47 pm

It depends on the individual database. Always be sure you have a backup before you upgrade.