Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 415228

Summary:	Slow "Open Type" results
Product:	[Eclipse Project] JDT	Reporter:	Missing name Mising name <im.god>
Component:	Core	Assignee:	JDT-Core-Inbox <jdt-core-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P3	CC:	jarthana, stephan.herrmann
Version:	4.3
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Missing name Mising name

2013-08-16 09:32:53 EDT

I have a maven project with several submodules. This project is pretty big, along with its big list of JAR dependencies.

When I do an "Open Type" or "CTRL + SHIFT + T", the results of my search are pretty slow. It always does an indexing, searching, and results don't appear until maybe 10 seconds later.

If I use a "working set" and just include the source code in my workspace, the results show up at an acceptable speed. As I type into the text box, results show up and narrow as more letters are typed in. If I don't use a "working set" (which include all the JARs), the results don't show up until 10 seconds later when I have stopped typing.

So it seems like Eclipse 4.3 is having trouble searching through the amount of JARs that I have in my workspace. This performance issue was not present in INDIGO or earlier.

SYSTEM:
Windows XP SP3 (3gb RAM)
JDK 1.6
Eclipse 4.3 (-Xms512m -Xmx896m -XX:+UseParallelGC -XX:PermSize=256M)

Comment 1 Stephan Herrmann

2013-08-17 05:45:41 EDT

Could this be an interaction between Maven and JDT?

To verify whether JDT is behaving well could you please:
(1) refresh (F5) all projects in your workspace
(2) wait until all rebuilding etc. by m2e and JDT is done
(3) invoke "Open Type" and narrow down the result to one class
(4) repeat (3)

If (4) shows acceptable performance you may want to check which particular
action causes the observed slow-down.

Also observing the heap status (windows>preferences>general) might give a hint.

Comment 2 Missing name Mising name

2013-08-19 10:02:57 EDT

(In reply to comment #1)
> Could this be an interaction between Maven and JDT?
> 
> To verify whether JDT is behaving well could you please:
> (1) refresh (F5) all projects in your workspace
> (2) wait until all rebuilding etc. by m2e and JDT is done
> (3) invoke "Open Type" and narrow down the result to one class
> (4) repeat (3)
> 
> If (4) shows acceptable performance you may want to check which particular
> action causes the observed slow-down.
> 
> Also observing the heap status (windows>preferences>general) might give a
> hint.

For maven, I am not using m2e. I am using the external Maven Eclipse plugin (2.8).

At startup, my heap status shows up as 106. Doing my normal routine of Maven, project clean, refresh, the heap jumped to 200 but settled back down to 107.

Doing the above steps, I am still experiencing slow results.

Comment 3 Missing name Mising name

2013-08-28 09:17:52 EDT

Just to provide some more feedback.

I closed out all of my submodules except for one. It still has its maven dependencies as JARs in the "Referenced Libraries" section. I performed "Open Type" and results came back within 3 seconds, which is acceptable.

I then opened up the next submodule. I performed "Open Type" again and the time it took the results to come back almost doubled.

In my original scenario, I had 9 submodules so it took 10+ seconds for any result to come back.

Comment 4 Missing name Mising name

2013-09-05 15:05:32 EDT

Tested this on Ubuntu and there was no issue with "Open Type" slowness. It seems to be on Windows only.

Comment 5 Missing name Mising name

2013-09-23 13:47:51 EDT

Slow on Windows 7 as well.

Comment 6 Eclipse Genie

2019-11-29 13:24:56 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.