Bug 11272 - slow context assist on method/field-rich classes
Summary: slow context assist on method/field-rich classes
Status: RESOLVED DUPLICATE of bug 6866
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M4   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-03-13 11:54 EST by Vladimir Grishchenko CLA
Modified: 2002-03-20 14:29 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 Vladimir Grishchenko CLA 2002-03-13 11:54:59 EST 
I noticed that the time to show a pop-up context assist menu is proportional
to the number of methods/fields (declared and inherited) in a class. While
can be understood, this becomes pretty painful for rich classes (think
Swing). It takes about 6-10 seconds with CPU usage at 100% to display the
box for JDialog, for example, and for a simple class that has 20-30 methods
it's almost instantaneous on a 800 MHz P3 running Win2k and Sun's 1.3.1.
Looks like the performance is not linear, it might also be related to
traversing the hierarchy up.
Comment 1 Vladimir Grishchenko CLA 2002-03-13 11:59:27 EST 
More info: the best way to reproduce is to enable auto-activation and press "." 
after a variable.
Comment 2 Erich Gamma CLA 2002-03-19 11:49:27 EST 
moving to core for first investigations
Comment 3 Vladimir Grishchenko CLA 2002-03-19 13:05:29 EST 
Performance much improved in 20020214, so looks like this bug can be closed...
Comment 4 Philipe Mulet CLA 2002-03-20 04:59:08 EST 
Vladimir - which built did you this in originally ?
Comment 5 Vladimir Grishchenko CLA 2002-03-20 11:30:14 EST 
20011219
Comment 6 Philipe Mulet CLA 2002-03-20 11:35:09 EST 
Ok, makes sense, we did indeed change the method argument name retrieval since 
then to address the perform issue (see bug 6866).

Closing

*** This bug has been marked as a duplicate of 6866 ***