|
| Re: CDT indexer slows down Eclipse [message #537262 is a reply to message #537230] |
Tue, 01 June 2010 17:35   |
 Michael Jackson
Messages: 28
Registered: July 2009 |
Junior Member |
|
|
You probably want to turn OFF the automatic indexing and have it index on
files saves only.
Also you may want to turn OFF automatic code suggestions and instead link
code completion to a manual keystroke (CTRL + SPACE) instead. This will help
improved the speed of the editor. You also may want to increase the minimum
amount of ram the the Eclipse App is going to use by editing the eclipse.ini
file. I usually bump it to at least 512 MB with a MAX of 1GB.
Mike J.
On 6/1/10 12:01 PM, in article hu3at2$4t9$1@build.eclipse.org, "Danilo
Turina" wrote:
> Since some time (3/4 years) I tried multiple times to use Eclipse with C++.
> Most of the times I had to give up because of the slowness of the thing that
> was not worth the additional features offered.
>
> Lately (6+ months) I'm using Eclipse (with satisfaction), but I have yet a
> problem with the indexer.
>
> Despite having an adeguate machine Intel Core2 Duo E6550 with 2Gb RAM, on a
> subset of the files I work on, the indexer slows down (sometimes I've the
> impression it's blocked) and this causes the whole eclipse to slow down, so
> that every 3/4 seconds the editor freezes for about 2 seconds.
>
> This way I can't work at all.
>
> At this point there's no way to stop the indexer (I press the red button, and
> it says it's stopping it, but it takes loooong time to stop).
> The only possibility I have is to restart Eclipse.
>
> The problem disappears if I disable automatic indexing ("Automatically update
> the index" in Preferences/C++/Indexer).
>
> Anybody with an idea on how solving this problem?
>
> Alternatively, is there a way to "lower the priority" of the thread that
> handles indexing (if the indexing is blocked or takes long, I don't care too
> much at condition that I can continue using the editor)? Is there a way to
> stop it?
>
> Some additional information:
>
> 1) I work with Windows XP (updated to latest patches)
> 2) I have updated my Sun's Java installation to 1.6.0_20
> 3) my eclipse.ini content:
>
> --launcher.library
> plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.0.200 .v20090519
> -startup
> plugins/org.eclipse.equinox.launcher_1.0.201.R35x_v20090715. jar
> -product
> org.eclipse.epp.package.cpp.product
> --launcher.XXMaxPermSize
> 256M
> -showsplash
> org.eclipse.platform
> --launcher.XXMaxPermSize
> 256m
> -vmargs
> -Dosgi.requiredJavaVersion=1.5
> -Xms256m
> -Xmx768m
>
>
>
|
|
|
|
|
| Re: CDT indexer slows down Eclipse [message #538394 is a reply to message #537262] |
Mon, 07 June 2010 14:39 |
Danilo Turina
Messages: 4
Registered: June 2010 |
Junior Member |
|
|
| Michael Jackson wrote on Tue, 01 June 2010 13:35 | You probably want to turn OFF the automatic indexing and have it index on
files saves only.
|
As I said in my previous message, I had to turn automatic indexing off in order to work-around this issue, but I don't know how to "have it index on
files saves only", since on preferences I see "Update index immediately after every file save" grayed if "Automatically update the index" is not checked.
| Michael Jackson wrote on Tue, 01 June 2010 13:35 | Also you may want to turn OFF automatic code suggestions and instead link
code completion to a manual keystroke (CTRL + SPACE) instead. This will help
improved the speed of the editor.
|
I was sure to already configured Eclipse that way: that was not true, now I have disabled automatic code suggestions, leaving only Ctrl+Space to trigger auto-complete.
The problem, anyway is that the slowness happens even if I just move the mouse around, so I don't think it's related to auto-completion.
| Michael Jackson wrote on Tue, 01 June 2010 13:35 | You also may want to increase the minimum
amount of ram the the Eclipse App is going to use by editing the eclipse.ini
file. I usually bump it to at least 512 MB with a MAX of 1GB.
|
Well, the initial configuration of Eclipse was very low as for the RAM allowed for Eclipse to use (and I had heap overflow problems).
I tried to just bump it up to 1Gb max (-Xmx1024m), but Eclipse failed to start (just a dialog box with all the starting parameters of Eclipse was shown), so I had to decrease it a bit (that's the reason of -Xmx768m).
| Michael Jackson wrote on Tue, 01 June 2010 13:35 |
Mike J.
|
Thank you for your suggestions.
|
|
|
Powered by
FUDForum. Page generated in 0.01951 seconds
] 
Search
Help
Register
Login
Home
