Community
Participate
Working Groups
The "Team -> Syncrhonize Workspace" for a git project is very slow. I have measured a time for 2 minutes and 36 seconds for the Eclipse ID to respond and it consumes 100% of a CPU core during that time. It used to take few seconds.
(In reply to Panos Kavalagios from comment #0) > It used to take few seconds. ... used ... but WHAT is happened on your side? New egit version? New Eclipse version? Different project to synchronize? More code in the project? A little bit more info would definitely help.
Same project and no change. The change from yesterday in the system was the updated: ffmpeg-libs-3.1.8-1.fc25.x86_64 libavdevice-3.1.8-1.fc25.x86_64 ffmpeg-3.1.8-1.fc25.x86_64 which I don't believe to affect Eclipse/git. Git was updated on May 16th to git-2.9.4-1 from git-2.9.3-3, but the issue is observed today with many local changes. Indeed, there are 6466 outgoing changes in the sync view and that's the great difference and not a typical scenario. I have reduced the size of the local changes to 30 and it is very fast again. So, we can say it is slow when there are many local changes.
Which EGit version are we talking about exactly? What model providers are enabled? Is it any better with EGit nightly? (There has been a recent change in that area that was supposed to improve performance; see bug 516358.)
I am using latest Eclipse Java EE Neon R3 (4.6.3) fully updated with: Git integration for Eclipse 4.6.1.201703071140-r The option "Allow Models" in Team -> Git -> Synchronize is enabled. I have installed the nightly built: Git integration for Eclipse 4.8.0.201705221216 to no avail. In fact, it makes things worse. It now requires 3 minutes and 26 seconds to display the synchronise view. The 4.8 version is about 40% slower than the previous version 4.6.1.
See bug 537288: with Photon/EGit 5.0, Panos' use case now appears to take more than an hour. Still unclear why. It's even unclear whether the problem is in EGit or Team. Deeply nested maven projects may have something to do with it; or perhaps simply nested projects.