Bug 92383

Summary:

Code completion is slow on types in big workspace [code completion]

Product:

[Eclipse Project] JDT

Reporter:

Tobias Widmer <tobias_widmer>

Component:

Core

Assignee:

JDT-Core-Inbox <jdt-core-inbox>

Status:

RESOLVED WORKSFORME

QA Contact:

Severity:

normal

Priority:

Keywords:

performance

Version:

3.1

Target Milestone:

3.2 M6

Hardware:

OS:

All

Whiteboard:

Attachments:

Description	Flags
CPU Trace	none

Description Tobias Widmer

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

2005-04-22 11:01:53 EDT

Created attachment 20240 [details]
CPU Trace

Comment 2 Frederic Fusier

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