Vault Client Performance Issues

[jkonline]

We have been having issues with starting the vault client many months althought he problem seems to be getting worse. It can sometimes take several minutes to open the client with the screen freezing. For the last release the UI is a bit more informative and it seems to be a client side issue rather than sever side as the message that it hangs on is 'Looking for changes in working folders'

We are running the latest version of Vault standard and there is no Antivirus on the Server however there is on the client.

Our vault details are outlined below however a few of the folders have over 1,740 files in.

Revisions: 9366
Folders: 5479 (+1516 deleted)
Files: 66478 (+18103 deleted)
Tree Size: 1.97 GB
Disk Space Needed: 3.94 GB
Database Size: 603.7 MB

Are folder structure is a single trunk that we branch (new development) into a new folder each month (for releases and bug further fixes) only keeping the last 2 branches.

[lbauer]

Does the client freeze before or after logging in?

If you connect to our demo server, do you experience the same problem?

To connect your Vault client to the Demo Server:
•Launch the client.
•For Username enter:
guest1 through guest10
•Password should be the same as Username:
guest1 through guest10
•For Vault Server enter:
vaultdemo.sourcegear.com

[jkonline]

I was unable to connect to the server:

Unable to connect to http://vaultdemo.sourcegear.com/VaultService. No server was found at the specified URL. Please verify your network settings using the Options dialog under the Tools menu in the Vault GUI Client. Web Exception: Unable to connect to the remote server

However this could be our network setup as we have only ever connected to internal servers.

To answer your other question it happens after login.

When it is connecting and checking for changes how much write disk access is there as our virus scan is configured for on write scanning?

[jkonline]

I have looked at the virus scanner console window and it is not scanning files while it is looking for changes in working folders.

I have seen this post http://support.sourcegear.com/viewtopic.php?t=1450 which says

Some operations (like branch of a large directory structure) can result in large tree deltas. Also, the tree delta can be large if the client doesn't have an old version of the tree

This may be our issue as we do branch everything once a month. Developers typically only keep the last branch plus the trunck and we obliterate the older branches.

What do you think we should we set it too?

[lbauer]

Do you have a lot of working folders that belonged to branches that have been obliterated? It could be that the Vault cache still has information on these.

You could try clearing the client side cache, then resetting working folders for just the folders you use the most.

Close any open clients first.

http://support.sourcegear.com/viewtopic ... 13&t=11513