Vault Client V.Slow with 1600 files

uberbloke · Post by **uberbloke** » Tue Apr 24, 2007 6:14 am

We have a project that includes a folder of all the Stored Procs and this is currently at about 1600 files

Using the vault client is incredibly painful because it is soooo slooooow.

It takes an age to paint the screen and after any operation in that folder you have to wait an age for it repaint again....

Is there anything we can do to make this less painful.

FYI I have set logging to all and this is attached
All I did was start the client, it opens to the large folder, change directory to another folder and change back to the large folder. This took over 2min 30sec and was no better with logging off.

Client Information
Vault Client Version: 3.5.2.5087
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1006.73 MB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 3.5.2.5087
.Net Framework Version: 1.1.4322.2379
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 2.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2005 - 9.00.3054.00 (Intel X86)
Mar 23 2007 16:28:52
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)

License Information
2 serial number(s):
1 of 2: 10 users, expiring 15/04/2007
2 of 2: 5 users, permanent

lbauer · Post by **lbauer** » Tue Apr 24, 2007 7:44 am

You have a lot of files in the one folder. There aren't any errors in the client log. Is this new behavior in Vault 3.5.2?

Do you see this on all client machines or just certain machines? Or did you see the same problem in earlier versions of Vault?

uberbloke · Post by **uberbloke** » Wed Apr 25, 2007 7:07 am

We see this on all client machines.

This was slow in 3.5.1 and we had hoped things would be better in 3.5.2

I know there are no errors in the log. I included it to demonstrate the slowness, the log is nearly 3 minutes long and all I did was
open client (opens in stored proc folder)
pick other folder
pick stored proc folder
close client

and I did this as fast as possibly could (e.g the delays are not me waiting to do stuff!)

As an additional thing, the client is very slow when it looses focus, e.g. if it goes behind the code window and is then bought forward again, it takes an age to paint, this is only the case with the folder with the large number of files in.

As a trial I changed the working directory to be a folder local to my machine rather than the current network share, this had no effect on the slowness we are experiencing.

Hope this and the other information posted helps.

lbauer · Post by **lbauer** » Wed Apr 25, 2007 8:32 am

In your Vault Client Tools->Options->Local Files, do you have "Detect modified files using CRCs" enabled? This can cause a slowdown.

uberbloke · Post by **uberbloke** » Thu Apr 26, 2007 4:23 am

lbauer · Post by **lbauer** » Thu Apr 26, 2007 10:17 am

Other than break up the files into more folders, there's no further way to improve this is in the current version of Vault.

I'll log a bug to review this performance issue and optimize it for a future release.

achen · Post by **achen** » Mon Apr 30, 2007 4:48 pm

uberbloke,

I reported the same problem back in Feb. 2007, here is the link to the thread.

http://support.sourcegear.com/viewtopic ... 0316#30316

My workaround was NOT to use Vault to browse my large folders and instead use an external diff tool. It is still painful to commit files, but at least you only do it once until the next set of modifications.

Hopefully SG will have this fixed in the next update.