TFS and Visual Studio slow registration

Question

I am not familiar with Visual Studio or Team Foundation Server, but I have a development team who complain about very slow checks (a few minutes) in Visual Studio 2010.

Examination of the server and the database does not reveal any problems. The problem arises only in one specific solution. A problem can occur even for very small text files. The problem affects all users in the team.

Where can I start troubleshooting?

change Additional information

The project size is ~ 11.5 GB, consisting of 284,455 files and 52,186 folders. ~ 10 users are accessing them. I think that in terms of size, this is the largest project we have.

I'm not quite sure when the problem first appeared.

I am tired of reproducing the problem on my machine without success. So it looks like something related to local setup. I installed the plugins and extensions that the development team uses.

The same developers have no problems with other projects.

Answer 1

For those who experience great delays when you do something that requires interaction with TFS (check, register, add a new one, rename, move, something), there may be many areas in TFS that can cause a problem. In my case, even the simplest TFS interaction in Visual Studio involves waiting 5-10 seconds. I decided to examine it using Process Monitor and found that every time TFS does something, it will iterate over each individual file in the TFS workspace, regardless of which projects were opened, or Source Control Explorer or Team was opened Explorer While @reticentKoala, I had 100,000 files with a total of over 17 GB in my workspace.

This is definitely a bug in the TFS client code (I am running VS2013, and our IT staff has been updated to any version of TFS associated with it), but, fortunately, it detects some workarounds.

In my case, I work on numerous projects, but usually only one or two at a time. By creating the Archive folder in a regular working folder and moving any projects that I’m not actively working on, I was able to reconnect TFS at a reasonable speed.

If you are actively involved in a much larger project that you cannot move around perforce, I can only think about possible solutions, but the main idea would be to simply reduce the number of files in your active workspace or their presence on your local machine.

Answer 2

You checked the following post, specifically Joel Rondo's comment: Suggestions for troubleshooting a slow TFS server or: http://www.lostapalooza.com/?p=150

I would guarantee that large BLOB files are not actually stored on the TFS system. Instead, store links to them, and for this, use the website and sites for work.