Bug 92383 - Code completion is slow on types in big workspace [code completion]
Summary: Code completion is slow on types in big workspace [code completion]
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC All
: P3 normal (vote)
Target Milestone: 3.2 M6   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: performance
Depends on:
Blocks:
 
Reported: 2005-04-22 10:59 EDT by Tobias Widmer CLA
Modified: 2006-03-31 08:32 EST (History)
0 users

See Also:


Attachments
CPU Trace (8.42 KB, application/zip)
2005-04-22 11:01 EDT, Tobias Widmer CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tobias Widmer CLA 2005-04-22 10:59:39 EDT
I20050420-1200:

Steps to reproduce:
- Use fresh workspace
- Import all external plugins and fragments as linked binaries
- Create new plugin project with dependencies on all the plugins in the 
workspace
- Goto the generated plugin class, type 'private T<Ctrl+Space>

->Takes 16s inside CompletionEngine
->CPU trace shows that over 14s are spent in BinaryType#getFlags()
Comment 1 Tobias Widmer CLA 2005-04-22 11:01:53 EDT
Created attachment 20240 [details]
CPU Trace
Comment 2 Frederic Fusier CLA 2006-03-31 08:32:15 EST
Good improvement have been done in Code completion (+30% our last performance tests results for 3.2 M6).

I've followed comment 0 scenario and didn't longer notice hot spot in BinaryType#getFlags() method...

I also get completion proposals list in around 1s (except time for indexing)

Consider this bug fixed in 3.2 M6 => close as WORKSFORME