check in / check out - very slow (VS2010)

[ESimon]

Hi,

check in / check out tasks are taking very long (up to few minutes). I'm using VS2010 along with the classic client.

I hope you got some hints for me

Best regards
Simon

[lbauer]

What version of Vault are you using?

What operating system is the client on?

How many files are you checking in/out and how large are the files?

[ESimon]

Hi,

vault version: 4.1.4
OS: Win7 Prof 64

The files are pretty small (mostly I check in/out only one file at the same time).


Best regards
Simon

[lbauer]

How long does it take to checkout those files?

When you checkout files with the Vault GUI Client, is that also slow?

[ThomasH]

We have the same problem in vs 2010 with the enhanced client( 5.0.4.18845). Check out is fast, check in needs about 60 seconds to build the change set in the dialog, which is popping up. With the gui client everything is ok, no delay to build the change set. A refresh in vs 2010 is faster than the check in dilaog to update the change set.

[ESimon]

it takes about 60-120 seconds (vs and vault client gui).

[lbauer]

We haven't tested Vault 4.1.4 with VS 2010 or on Windows 7, so it's not fully supported.

We've had other reports of slow performance with VS 2010 and haven't determined the cause yet.

However, if you're getting slowdowns in the GUI Client, we can look into that.

First, enable debug server logging in the Admin Web Client under Server Settings->Logging->Log Level. It's called sgvault.log and is in %windir%\temp\sgvault on the server machine.

Then enable logging for all events in the GUI Client. Open the Vault GUI Client and hold down the following keys on your keyboard: Control-Alt Shift F12.

Reproduce the problem, then send me copies of the logs. Let me know what user was experiencing the error and what time the error occurred so I know where to look for in the logs.

The Vault GUI Client log is called VaultGUIClient.txt and is in your user's temp directory, which on Win 7 would be: C:\Users\User\AppData\Local\Temp

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

[tresstylez]

Was this issue ever 'resolved'? If so, how? I'm facing a similar issue with Windows 7 in my org.

Please advise.

Thanks.

jg

[lbauer]

We're still gathering information and testing. What version of Vault are you using? Are you using the Enhanced or Classic Client for integration? Are you on a 64-bit Win7 machine?

We have identified one cause of significant slowdowns -- Vault Enhanced Client diagnostic logging. Diagnostic logging is enabled/disabled in VS 2010 under Tools->Options->Source Control->Integration Options.

However, users have reported slowdowns with logging turned off.

Another suspect is the Vault VS Enhanced Source Control Toolbar. Some users have found performance improved when they didn't display the tool bar, but our in-house results haven't been the same. You can disable the tool bar in VS 2010 under View->Toolbars.

[tresstylez]

Thanks for the reply, Laura.

I'm not sure what the difference is between 'classic' and 'enhanced'. Our users are running VaultClient_4_1_3_18336. The user with the issue only experienced the problem when IT upgraded him to Windows 7 Enterprise (32 Bit).

I'll have him try the options you sent...

Thanks.

jg

[lbauer]

The Classic and Enhanced Client are two different styles of integration which use different Microsoft APIs.

http://support.sourcegear.com/viewtopic ... 672#p39036

In limited testing of VS 2010 with Vault Classic Client integration on one user machine, the memory usage was greater than with the Enhanced Client or with no integration.

Also our limited tests showed that Visual Studio 2010 memory usage increased as we were using Visual Studio, with or without integration, so that could be contributing to the slowdowns.