`team-explorer-everywhere` operates extremely slow on huge projects

[yspinner]

I have a general Eclipse project with 96,000 text file in it.
I use Eclipse 202206 and Team-Explorer-Everywhere ver 14.139, on Java 11.
I use a VM in Azure with 2 CPU and 8GB memory (B2MS).

It takes 34 hours!!! to share that project into TFS (it is realy fast to import the project from TFS into a new workspace in Eclipse)

I tried testing with different size projects:

1. With 1000 files -> it took 2 minutes.
2. With 26,000 files -> it took 4 hours.
3. I tried to use ver 14.138 to 14.135, all the same results.

It seems to go up exponentionaly has more files are in the project.
Any ideas what cuaes the issue?
Anything I can change in teh configuration to speed it up?

[eric-milles]

Hard to say off the top. Sharing a project is broken into multiple steps. Can you use jvisualvm or something to capture some thread dumps during the long-running stage of the process? You only need to find the thread that is running "com.microsoft.tfs" frames.

[awilkins]

Any ideas what causes the issue?

This is caused by the design of TFVC, which is heavily informed by the design of CVS ; which is itself an extension of RCS, which at the time of writing is a 43 year old version control system.

There's no fixing this ; it would require fundamental rework of the data structures and protocols used by TFS.

I recommend you try Git instead - which copes well with the very large Linux kernel tree which was 87k files and 39M lines of code as of December 2024.