Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » EGit » CPU consumed with many projects
CPU consumed with many projects [message #579037] Fri, 09 April 2010 16:07 Go to next message
David McNeil is currently offline David McNeil
Messages: 6
Registered: April 2010
Junior Member
I am trying to use EGit with a git repository that has ~20 Eclipse projects. After importing these projects into Eclipse, if I select a project and choose Team : Commit... then my CPU is consumed for many minutes before Eclipse responds.

I am curious if this is a known issue or perhaps there is a workaround for making EGIt work well with many projects in a single repository?

This occurred on:
* Windows 7 Professional - 64 bit
* Eclipse 3.5.2
* EGit 0.7.1

Thank you.
-David McNeil
Re: CPU consumed with many projects [message #579087 is a reply to message #579037] Sat, 10 April 2010 05:01 Go to previous messageGo to next message
Robin Rosenberg is currently offline Robin Rosenberg
Messages: 317
Registered: July 2009
Senior Member
David McNeil wrote:

> I am trying to use EGit with a git repository that has ~20 Eclipse
> projects. After importing these projects into Eclipse, if I select a
> project and choose Team : Commit... then my CPU is consumed for many
> minutes before Eclipse responds.
>
> I am curious if this is a known issue or perhaps there is a workaround for
> making EGIt work well with many projects in a single repository?

Using Linux is one way :) Checking the status of all files takes a lot
of time and Linux is much faster.

The other answer is that we probably can make things faster, but the 20 or
so second delay when committing with 20-25 projects has not forced me there
yet. One of the reasons for slow speed is that we do not trust that Eclipse
is up-to-date on what resources have been changed on disk, so we force a
check and the major reason is that most EGit, and in particular the
developers use C Git every now and then, which means that Eclipse will be
unrefreshed very often. There are multiple ways of dealing with this and we
haven't made our minds up on how yet. When all operations are usable (merge
in particular), we may be able to start trusting Eclipse notion of
modification status.

-- robin
Re: CPU consumed with many projects [message #579271 is a reply to message #579037] Mon, 12 April 2010 10:18 Go to previous message
David McNeil is currently offline David McNeil
Messages: 6
Registered: April 2010
Junior Member
Robin - I tried the nightly build from yesterday and it seems the issue is resolved. Invoking the "Commit..." option in Eclipse now only takes ~6 seconds.

Thank you!

-David
Previous Topic:CPU consumed with many projects
Next Topic:Delete project from multiple project repository
Goto Forum:
  


Current Time: Wed Jul 23 05:52:59 EDT 2014

Powered by FUDForum. Page generated in 0.02037 seconds