Bug 195423 - [content assist] computes type hierarchy when filtering prefixes
Summary: [content assist] computes type hierarchy when filtering prefixes
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.4 M1   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-07-04 13:56 EDT by Markus Keller CLA
Modified: 2007-07-10 11:11 EDT (History)
0 users

See Also:

Attachments
CPU Trace (106.62 KB, text/html)
2007-07-04 14:01 EDT, Markus Keller CLA 		no flags Details
View All 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 Markus Keller CLA 2007-07-04 13:56:51 EDT 
N20070704-0010

For unknown reasons, my content assist became unusably slow when I invoked it on a Composite and then started filtering the proposals:

    void m(Composite c) {
        c.|   // press Ctrl+Space here and then type "g"
    }

I took a performance trace in which I found that much of the time was burned in the type hierarchy computation triggered by ParameterGuessingProposal.computeReplacementString()

I think this has been introduced the fix for bug 188851.
Comment 1 Markus Keller CLA 2007-07-04 14:01:16 EDT 
Created attachment 73051 [details]
CPU Trace

I guess this is not the only cause of the slowness I see (I also have a heap > 180 MB with 1 open editor), but it's probably an important part.
Comment 2 Dani Megert CLA 2007-07-10 10:04:30 EDT 
- Composite is org.eclipse.swt.Composite.
- parameter guessing must be enabled

Fixed in HEAD.