Select All in Pending Change Set takes ~10 Minutes!!

[Chiramisu]

After a recent update to Vault 6 from 3.1.8, one of our engineers brought to my attention that it takes him about 10 MINUTES just to do a Select All on his "Pending Changes Set" tab. I found this question (Select All in Pending Change Set takes forever!) which we went through pretty thoroughly but didn't find any real help.

I'll try to answer some of the questions that were asked in that thread as well.
The set we're trying to select is a folder with a "Tree size" of a hair over 100 MB, and an estimated 6-7,000 files. The working directory is set at the Branch level.

I have log files for you if you want them. Just tell me where to send them. Thanks.

[lbauer]

Is this slowdown in the Vault client or in Visual Studio? We've had other reports of slow performance in Visual Studio and are working on a fix.

[Chiramisu]

In the Vault Client.

[lbauer]

How many items are in the Pending Change Set?

[Chiramisu]

As mentioned in the OP, an estimated 6-7,000 files in the change set perhaps. There is no counter for this that I'm aware of, so this is just a rough estimate.

[lbauer]

We made a number of changes to the Pending Change set, and in the process optimized it for about 1,000 items. We thought that would cover most use cases. However, if you have several thousand checked out, it does make the client rather slow.

I've logged feature request 16602 to optimize for more items in the Pending Change Set..

One option would be to checkout just the files that are being worked on.

Another option is to use CVS mode, which makes files writable on disk. A file does not need to be checked out before editing. Only modified files are added to the Pending Change Set. This setting is in the Vault Client under Tools->Options->Concurrent Development Style.

[Chiramisu]

Would this cover the case where the change set is a direct result of creating a new branch? Because that is where these "changes" are coming from in most cases as far as I understand it.

Thanks for logging the feature request. When our engineer has some time, I'll ask him to look into trying the CVS mode as a possible solution.

[lbauer]

Earlier, I checked out a project with more than 3,000 files, and all those items were listed in the pending change set. Any pending change set operations were slow, as you have observed.

Branching was different. Using VSS mode, I tried branching a project that has more than 3,000 files. Nothing was added to the pending change set and the transaction took about 10 seconds.

I'm not sure why branching would add so many items to the pending change set. Perhaps you could send a screenshot or we could schedule a remote session where I can take a closer look.

Email me at support at sourcegear.com, ATTN: Linda.

Please include a link to this forum post.