Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cdt-dev] How can I prevent the indexer taking over the entire CPU?
To understand what multiple Eclipse CPU-bound threads are doing you can capture 3-4 stacks using jstack.

-sergey

On Wed, Mar 16, 2016 at 6:49 AM, Steve Lorimer <steve.lorimer@xxxxxxxxx> wrote:
Hi all

As suggested by Sergey Prigogin, I ran iotop (and htop) when I next experienced this problem.

I captured several screenshots.


In the last screenshot you can see that Eclipse has now completely stopped responding, and Gnome shell is asking if I want to kill it.

iotop shows 0 disk usage at all.
htop shows 7 java threads running at 100% each

I am 100% sure that this high CPU load making my computer unresponsive only happens when the indexer kicks in. However, it is only occasional - sometimes the indexer will start, run and complete without causing this CPU load.

4 minutes passed between the period when I took the first screenshot and the last screenshot. During this time I wasn't using Eclipse at all, as it was completely unresponsive.

Any insight would be greatly appreciated!

Thanks in advance
Steve



On 15 March 2016 at 13:28, Sergey Prigogin <eclipse.sprigogin@xxxxxxxxx> wrote:
Indexer is single threaded and cannot possibly take over all four cores of Core i7-4790. The problem you are seeing is probably I/O related. I recommend using iotop to investigate the issue.

-sergey

On Tue, Mar 15, 2016 at 11:13 AM, Steve Lorimer <steve.lorimer@xxxxxxxxx> wrote:
Hello all

Is there anything I can do to prevent the indexer from periodically taking over the entire CPU?

Every now and then I will see indexer running in the Progress tab, and my computer will become totally unresponsive. "top" shows the Java process running at several hundred percent.

I am running Eclipse IDE for C/C++ Developers

Version: Mars.2 Release (4.5.2)
Build id: 20160218-0600

This is on 

Ubuntu 14.04
Core i7-4790 CPU @ 3.60GHz
8GB RAM
150GB SSD

My indexer settings are:

Indexer options 
Allow heuristic resolution of includes
Skip files larger than 8MB
Skip included files larger than 16MB
Indexing strategy
Automatically update the index
Cache limits:
Index database cache:
Absolute limit: 4096MB
Limit relative to max heap size: 50%
Header file cache:
Absolute limit: 4096MB

I have the following settings for eclipse.ini

$ cat /opt/eclipse/eclipse.ini 
-startup
plugins/org.eclipse.equinox.launcher_1.3.100.v20150511-1540.jar
--launcher.library
plugins/org.eclipse.equinox.launcher.gtk.linux.x86_64_1.1.300.v20150602-1417
-product
org.eclipse.epp.package.cpp.product
--launcher.defaultAction
openFile
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-XX:PermSize=2G
-Dosgi.requiredJavaVersion=1.7
-XX:MaxPermSize=4G
-Xms4G
-Xmx8G

Thank you in advance, any help is very much appreciated

_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev


_______________________________________________
cdt-dev mailing list
cdt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cdt-dev

Back to the top