Community
Participate
Working Groups
I have a repository with 15 odd eclipse projects and around 7500 java files. After a merge I selected the Merge-Tool option which brought up a Progress information dialog for more than 10 minutes, using git native the operation is near instantaneous before the first merge conflict prompt comes up. The progress information seemed to show that it was inspecting every file in the workspace.
Which build? The latest nightly? Potentially related to this... http://dev.eclipse.org/mhonarc/lists/jgit-dev/msg00780.html
I guess this is related to current performance problems regarding TreeWalks & FileTreeIterator. Although I am not sure why we should check complete trees when it is about resolving a conflict on a known path. I'll see if this can be reproduced on a big repo.
Sorry, build version was 0.10.0.201011192. Whats odd is that it was scanning untracked files as well! In the test I did, I did a right-click merge-tool on a folder rather than a specific file with conflicts.
Code review at http://egit.eclipse.org/r/#change,2390
Fixed, thanks.
The performance is much improved - about 1 minute to scan all projects. The progress information is still showing files that are in the .gitignore (class files that have been built by ant).
Code review (In reply to comment #6) > The performance is much improved - about 1 minute to scan all projects. > > The progress information is still showing files that are in the .gitignore > (class files that have been built by ant). This is of course confusing. Code review at http://egit.eclipse.org/r/#change,2406
We now skip ignored resources when building the tree walk.
With the latest change the merge-tool shows up almost instantaneously!