Vault Performance

[jkonline]

Recently our vault seems to be crawling along, taking several minutes to commit. I have run through he performance threads and these helped a bit but still a big issue.

Our DB has grown over the last year. We keep a master trunk for dev work and then create a new branch after each release for bug fixes. We only keep the latest branch the other branches are initially pinned and later deleted. It takes now about 8 minutes to get a fresh copy of everything from our master branch in vault.

February 2011

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

February 2012

Revisions:15656
Folders:11443 (+8519 deleted)
Files:126816 (+105772 deleted)
Tree Size:3.23 GB
Disk Space Needed:6.45 GB
Database Size:1.06 GB

[lbauer]

Your database is not particularly large; we've dealt with Vault databases that are over 50 GB, so that's only one consideration when there are performance issues.

As a first step, could you provide us with the system information under Help->Technical Support in the Vault Client?

[jkonline]

Client Information
Vault Standard Client Version: 5.1.1.19215
.NET Framework Version: 2.0.50727.5653
Operating System: Microsoft Windows XP Professional
Service Pack: 3.0
OS Version: 5.1.2600
Total Physical Memory: 1.99 GB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Server Version: 5.1.1.19215
.NET Framework Version: 2.0.50727.3625
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.4035.00 (Intel X86)




License Information
1 serial number(s):
1 of 1: 10 full users, permanent

[lbauer]

First, we'd recommed running database maintenance, per this KB article:

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

Also, we'd like to see a copy of the Vault Server log, in case there are errors affecting performance. It's called sgvault.log and is in %windir%\temp\sgvault on the server machine. Send at least a couple days of logs.

Send at least a couple days of logs (zipped up) to support at sourcegear.com, Attn: Linda. Please include a link to this forum post.

[jkonline]

I have emailed the logs and will run the performance bits later today

Thanks

[lbauer]

No serious errors in the logs. Let us know how the database maintenance goes.

It takes now about 8 minutes to get a fresh copy of everything from our master branch in vault.

How big is this get -- how many files, size on disk?

[jkonline]

Our users often don't use the vault client as it is too slow on their PC's (typically 4 minutes to open and connect) so opt to either use vault integration in visual studio. This I guess why the logs are full of login and out is due to opening and closing of projects.

A single branch is 1.76 GB and 35,422 Files. The build machine will get a fresh copy for each build hourly however as a user it is rare we requested everything. This was one example of the issues we are having.

Committing a file can take a several minutes hanging on "Ending Transaction". Sometime a show differences can be instant however many users complain that this triggers "Retrieving Repository Structure" and brings it to a halt for a few minutes.

Last night we ran the maintenance as outlined in the post you linked too however this failed to help.

Hope this helps explain the issue.

[lbauer]

What are the specs of your Vault Server -- RAM, CPU, etc?

Is it 32-bit or 64-bit?

[kkchan]

I am facing the same problem. It just happen suddenly. My machine is 32 bits, using Vault 4.1.4.18402. I checked sgvault, it just shown, user login, then nothing.

[kkchan]

Hi
I found the workaround to rename my C:\Users\<user name>\AppData\Local\Sourcegear\Vault_1 folder and relaunch the Vault Client again.
May I know what is the issue?

[lbauer]

If users are experiencing slow logins, they can try disabling the setting in the Vault Client under Tools->Options->Network Settings-> Request database delta on repository cache miss.

Usually a delay on login means the client is waiting on the server to compute a delta in the database. This can sometimes be a slow operation, and "unchecking" the option can sometimes lead to improved performance.

When you deleted the client-side cache, it caused the server to send a new tree structure to the client, rather than slow things down by diffing the cached tree with the repository tree. However, try changing the option described above rather than deleting the cache.

[kkchan]

Hi
For your info, some user still unable to retrieve repository structure after tried clear the cache or disable database delta setting.

Please advice. tq

[jkonline]

If users are experiencing slow logins, they can try disabling the setting in the Vault Client under Tools->Options->Network Settings-> Request database delta on repository cache miss.

This made a few minutes startup into a few seconds. Will it have any side effects?

[lbauer]

Glad that helped. Since users are getting the whole tree from the database now, more data is coming down. Just keep an eye on network I/O and throughput, especially with very large repositories.