Select All in Pending Change Set takes forever!

[neal007]

In Vault Client I'm trying to select all files by pressing CTRL + A as there is no root checkbox to select everything. I need to undo the checkout of a lot of files I was preparing to run a conversion on. It takes forever and 3 days to do a CTRL+A on a lot of files. Is there any way to speed this up? Maybe you're missing a BeginUpdate/EndUpdate call that's really slowing things down as it's trying to render on each selection?

[Beth]

I tried this out and am not getting the same results, so I'll need to get some more details about this.

Can you tell me how many files you have checked out that you are trying to select?

Where exactly are you trying to select all the files? Is it the Pending Change Set window in a Vault GUI client, or is it the same window in Visual Studio? If it's in Visual Studio, which client are you bound to there?

Can you post a screenshot?

[neal007]

Pending change set tab on the bottom of the Vault GUI client, several hundred files, i.e. multiple full project checkouts preparing for a 3rd party component upgrade of files.

My guess is that when each row is checked "stuff" such as toolbar buttons etc. is updating. In the case of a CTRL+A or clicking the select all button then the UI should be suspended to prevent this for a faster mass selection.

[Beth]

I next tested on a Windows 7 virtual machine (under powered) and checked out our entire demo repository, and it could select that as well in about 10 seconds.

Do you possibly have antivirus scanning your cache or working folders? That could slow it down.

Would it be possible to have you start debug level logging on the client by pressing Ctrl - Alt - Shift - F12, and then try a Ctrl A? After it has everything selected, send us the client log file found at %temp%/VaultGUIclient.txt in an email to support at sourcegear.com (attn: Beth) with a link to this forum thread.

[neal007]

The dev folders are excluded, I'll find the cache location and make sure it's excluded as well. I'll see what I can do to provide you the information requested when able.

[Beth]

Are you working in CVS mode, or VSS mode, or some combination? Those settings are found in the Vault - Tools - Options - Concurrent Development Style.

How many working folders do you have set? By that, I mean, do you just set one at $ and let everything inherit down from there, or do you set individual working folders on $/Project2, and a different, non-inheriting folder at $/Project2, and maybe another non-inheriting folder at $/Project2/branch 1.0?

[neal007]

VSS style. We set a working path on $ and check the option for force everything below to inherit. I had about 7-10 complete areas checked out to perform the update as a batch (DevExpress project converter).

[Beth]

In the Vault Tools - Options - Network Settings, do you have the option "Request database delta on repository cache miss" checked? If so, try unchecking that option and see if the select all works faster.

Do others at your company have the same issue?

[neal007]

Yes, that option IS checked. I'm the only one that does the mass project conversions. I have 35 MB internet speeds if that makes a difference. Can you tell me what this feature does and the pro's/con's of having it checked or not?

I can't try it right now as I can't do the mass checkouts. I'll give it a try over the weekend.

[Beth]

When the repository revisions that is stored in memory is many versions out of date, the client requests a database delta. When 'Request Database Delta on Repository Cache Miss' is turned off, a full tree is retrieved instead. There's an entry on that setting in the manual as well that may help with understanding it: http://download.sourcegear.com/misc/vau ... tings.html.

Are you using check boxes in your pending change set?

[neal007]

Since the database delta default option is checked, I'll leave it as is.

I am using the pending change set in the Vault Client so yes, all rows have a checkbox but I'm not checking them. I'm using CTRL + A or clicking the select all button on the toolbar.

[Beth]

Since I still can't reproduce this, I think we should get some debug level logging going and have you send me the log files during a select all using Ctrl - A.

Server level logging:
1) Go to C:\Windows\temp\sgvault and rename the log sgvault.log. This will force Vault to create a new one that will just cover the information that's needed.
2) Open the Vault admin web page and click on the logging link.
3) Change the logging level from Quiet to Debug.
4) Change the archive level from weekly to daily.
5) Click Save. All users will be disconnected and need to login again.

Client-side logging:
1) Open a Vault GUI client, but don't log in.
2) Press the key combination Ctrl - Alt - Shift - F12.
3) In the lower left corner of the Vault window will be a path listed for the log.
4) Now you may go to File - Connect to Server to login and continue your test.

You can either post the logs here or send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread and the log files.