[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [egit-dev] Slow update of changed-markers
|
2011/7/21 James Blackburn
<jamesblackburn@xxxxxxxxx>
See also:
On 21 July 2011 09:08, Klaus Reimer
<k@xxxxxxxx> wrote:
Hello,
I'm trying to use egit (1.0.0.201106090707-r with Eclipse 3.7) on a
pretty large project (113555 files in 12895 directories, total size of 2
GB). It's quite unusable. When changing a single file then egit needs
3-4 minutes to update the label decorations (100% CPU usage). I really
wonder what it is doing. Refreshing/Rescanning the whole project just
because one file changed? When I run "git status" on the command line
then I get a response in 1-2 seconds. Wouldn't it be better to run this
command when a file has changed and then parse the output and only
update the markers for the files listed by git status? Or maybe even
comparing the output with a previous cached output and only apply the
changes?
With the Mercurial Eclipse plugin I had the same problem with earlier
versions but they drastically improved it in later versions and the
decoration-updates after a file change only took a few seconds when I
tried it the last time. (I'm not using Mercurial for other reasons).
With SVN (Subclipse) it is also quite slow but not as slow as with egit
(Docoration-updates needs up to 30 secs).
Is there any chance this situation will improve in future egit versions?
I'd really like to switch from SVN to GIT but currently this performance
problem with egit is a show-stopper.
Yes, we will definitely work on these issues but there is no concrete schedule yet
as we are in the middle of vacation period and there are also other projects
eating capacity we could spend on egit development
As a workaround you may try to switch off label decorators
(Preferences > General > Appearance > Label Decorations > Git) and use the
git staging view instead, we found it's a lot faster than decorators in package explorer
