Eclipse Community Forums: EGit / JGit » CPU consumed with many projects

Help

Home

Home » Eclipse Projects » EGit / JGit » CPU consumed with many projects

Show: Today's Messages :: Show Polls :: Message Navigator

CPU consumed with many projects [message #526360]

Fri, 09 April 2010 20:07

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

[Updated on: Fri, 09 April 2010 20:08]

Report message to a moderator

Re: CPU consumed with many projects [message #526395 is a reply to message #526360]

Sat, 10 April 2010 09:01

Robin Rosenberg

Messages: 332
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

Report message to a moderator

Re: CPU consumed with many projects [message #526410 is a reply to message #526395]

Sat, 10 April 2010 15:31

Robin Rosenberg

Messages: 332
Registered: July 2009

Senior Member

Robin Rosenberg wrote:

> 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

Measuring on Linux gave me the following quickfix. A guess is that is
helps even more on Windows. If you can please test and provide feedback.

http://egit.eclipse.org/r/#change,538

strace-ing Eclipse indicates more opportunities exists :)

-- robin

Report message to a moderator

Re: CPU consumed with many projects [message #526417 is a reply to message #526410]

Sat, 10 April 2010 17:30

Robin Rosenberg

Messages: 332
Registered: July 2009

Senior Member

Robin Rosenberg wrote:

> Robin Rosenberg wrote:
>
>> 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
>
> Measuring on Linux gave me the following quickfix. A guess is that is
> helps even more on Windows. If you can please test and provide feedback.
>
> http://egit.eclipse.org/r/#change,538
>
> strace-ing Eclipse indicates more opportunities exists :)

You are going to love this one: http://egit.eclipse.org/r/#change,539

Despite all my bad excuses we had some really inefficient code in there.

-- robin

Report message to a moderator

Re: CPU consumed with many projects [message #526644 is a reply to message #526417]

Mon, 12 April 2010 13:49

David McNeil

Messages: 6
Registered: April 2010

Junior Member

Robin - Thank you for your responses. I will switch to the nightly build to see if your changes fix the issue for me.

Thanks.
-David

Report message to a moderator

Re: CPU consumed with many projects [message #526659 is a reply to message #526360]

Mon, 12 April 2010 14:18

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

Report message to a moderator