Performance and weird file status issue

bobogs · Post by **bobogs** » Thu Aug 25, 2005 7:12 am

I've been using Vault (Server 3.0.7, Client 3.0.7) for a few weeks now, and while I like it and it seems to work pretty well most of the time, sometimes it behaves oddly, and it's getting to be a bit annoying.

I imported many VSS projects into various Vault repositories, and the imports worked fine. My dev environment is Visual Basic 6 SP6. I am using Vault as my default SCC.

I've read that one of the benefits of Vault is that it's fast, but I just don't see it when I'm using the client or the Visual Studio integration. The web/sql server that's hosting the vault server web service and the database is a single cpu box, running Win2003Standard and SQL Server 2000, with 512mb of ram. There are several other IIS websites and sql server databases on this box, but none of them are hit very hard throughout the day. When i fire up the client on my pc, it might take 2 to 5 minutes before I'm ready to work with the selected repository...I see the Working statusbar message quite a bit. I also see the Ending Transaction statusbar message for a long time when I do a check in. Any suggestions on boosting the performance?

Secondly, there are times (not all the time, and I haven't been able to reproduce it on demand) when I check out one or two VB6 files (frm, frx, bas, cls) using the client, open the VB6 project, and when I switch back to the vault client, several other files which I have not touched in VB6 are either Renegade or Needs Merge. Is VB6 touching these files as the project loads, which causes them to be different than what vault thinks they should be?

Thanks for any help.
Gary

lbauer · Post by **lbauer** » Thu Aug 25, 2005 8:11 am

The first thing to do would be to review our KB article on Vault performance to see if any of the tips are helpful:

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

Review the Vault server log file to see if there are error messages or frequent server restarts.

Regarding the VB issue, users do sometimes get unexpected results when they use both the Vault GUI Client and IDE client for source control operations. A renegade or needs merged status can happen if the file timestamp has changed -- does this appear to be the case?

This may be hard to pin down if it's an intermittent problem.

dan · Post by **dan** » Thu Aug 25, 2005 8:46 am

One thing that might help your configuration is RAM. 512MB is pretty small for a server, especially if you have large trees. I'd recommend at least 1GB, and possibly 2GB.