Bug 50218 - Search is slow if eclipse started without -Xmx256M
Summary: Search is slow if eclipse started without -Xmx256M
Status: RESOLVED WONTFIX
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 3.0 M7   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-01-19 11:05 EST by Pascal Rapicault CLA
Modified: 2004-01-21 11:28 EST (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pascal Rapicault CLA 2004-01-19 11:05:56 EST 
In eclipse 3.0M6. 
Load the following projects from source
- org.eclipse.jdt.core
- org.eclipse.jdt.core.tests.compiler
- org.eclipse.jdt.core.tests.model

Create a new "JUnit Plug-in test" launch configuration
In the test tab, select "run a single test", select "search" for test class.

On a P4 2ghz 768Mo of RAM. The operation takes 3min and 27sec to complete if 
no -Xmx option is specified, whereas with this option set to 256M, the 
operation completes in 28sec.
Comment 1 Philipe Mulet CLA 2004-01-19 13:12:58 EST 
So ? This means search is memory intensive, which we knew already.
What is the problem ?
Comment 2 Pascal Rapicault CLA 2004-01-19 13:21:30 EST 
Sorry I did not know...

The problem is that you not necessarily start eclipse with -Xmx option, and 
such bad performances give a bad overall impression of the platform (I really 
waited for more than 3 min ! and I have a fast machine).

Maybe it is a UI responsibility problem where results could be shown as they 
are available.
Comment 3 Philipe Mulet CLA 2004-01-20 03:52:34 EST 
Eclipse is advertized to be run with more than VM's default memory.
Too bad the eclipse.exe cannot default to -Xmx256MB or better.
Comment 4 Philipe Mulet CLA 2004-01-21 11:28:12 EST 
Closing, no action planned.