Vault client unusably slow

[alan.bowens]

Hello,

My vault client has within the last couple of days become unusably slow - displaying folder contents, adding files, check-ins, etc all take far too long. My colleagues, with the same PC setup and running through the same router to the same repository, are having no problems. I have cleared my cache and wiped all subfolders under my local settings sourcegear\vault_1\client folder - none of this makes any difference. Any ideas?

Regards

Alan

The techy stuff:

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

Server Information
Vault Server Version: 4.0.6.15954
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft(R) Windows(R) Server 2003, Web Edition
Service Pack: 1.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2000 - 8.00.2039 (Intel X86)
May 3 2005 23:18:38
Copyright (c) 1988-2003 Microsoft Corporation
Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

License Information
6 serial number(s):
1 of 6: 5 full users, permanent
2 of 6: 5 full users, permanent
3 of 6: 6 full users, permanent
4 of 6: 5 web-only users, expiring 18/05/2008
5 of 6: 5 full users, permanent
6 of 6: 5 full users, permanent

[lbauer]

Enable client-side logging. That should give us more information:

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

Send the log zipped up to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[alan.bowens]

Hello,

I enabled client-side logging as suggested, but the app has been behaving itself flawlessly since the weekend. If the problem recurs I will submit a log file.

Thanks for your time.

[lbauer]

I call that phenomenon the "Tech Touch." As soon as tech support starts paying attention to a problem, the app starts behaving itself.

Let me know if we can be of assistance in the future.

[alan.bowens]

Well, this behaviour is back again. The attached log file was gathered while I checked-in a file, then attempted to browse the folder tree.

In the end I gave up and killed the process.

Alan

[lbauer]

We reviewed the client log and the client is busy with scanning the working folders and creating the checkout lists. There appear to be *a lot* of working folders and files checked out.

Try reducing the amount of checkouts, if possible, or unset some of the working folders you're not using, and see if that makes a difference. Also, if you're using "ghosted" files and folders in the file list/folder tree, turn that off as this also causes scanning of the working folders.

[alan.bowens]

Noted.

This particular project is a library that is built with a whole bunch of compilation options, which is why there are so many folders. I'll try to only check out the bits I'm actively working on.

I've also got ghosting on, so will try turning this off when working on this particular project.

Thanks for the info.

[lbauer]

Let us know if there's any improvement after you make the changes.