Vault check-in very slow with VS2010

[samward]

Hi,

I have recently upgraded my machine to VS2010 and Vault 5.0.3 (Desktop running Win7, server running Win2k3 and SQL2005). Since then I am finding that checking in changes very slow (in the order or 5-10 minutes) for small changes (5KB changed, 3 files). VS seems to lock up initially, then the begin transaction message will stay on screen for a while, and then the end transaction message will stay on screen for a while.

As best I can tell everything seems to be working, just very slow. It also only appears to be the check-in operation (or at least it is the only one I have noticed). Any idea what might be causing this / what other things I can check??


Cheers
Sam

[Beth]

Are you using the Vault Enhanced or Vault Classic Client? That information is found in VS Tools - Options - Source Control - Plugins.

If you check in a change using the Vault GUI client, is the speed faster?

[samward]

I am using the VS Enhanced Client.

When using the Vault GUI, it seems like both browsing the repository, as well as checking in a file takes much longer.

As an example, from the GUI Message log:
[18/05/2010 9:40:49 PM] Preparing data to begin transaction
[18/05/2010 9:40:49 PM] Beginning transaction
[18/05/2010 9:40:49 PM] Check in $/vs/Form1.cs
[18/05/2010 9:41:43 PM] Ending the transaction
[18/05/2010 9:42:46 PM] Transaction completed successfully

Where Form1.cs is a 2k file.

Cheers
Sam

[Beth]

Since you have slowness with the GUI client, let's focus on that, and once that's resolved I'll have you compare it to working in VS 2010.

If you go to Vault Tools - Options - Network Settings, what do you currently have set there?

Try changing your chunked encoding setting to see if checking in gets faster. If that doesn't help, try turning off the others, or turning them on if you already have them off.

Next, go to Vault Tools - Options - Local Files - Cache Location. Do you have a cache file limit set? If so, turn that off. By default it's turned off, but if you turn it on and set a limit, then Vault has to talk to the server more to get the information it needs, which could make it perform slower.

[samward]

I must appologise, but I have resolved the slowness.

While looking at the server (for other reasons), it turns out there was a process there leaking memory. Killed the process and everything came good.

I guess it was just a case of bad timing that it had reached a critical point at the same time as the Vault upgrade.

Thankyou for your assistance.

Sam

[Beth]

Thank you for the update. I'm happy to hear you're fully functional again.