Re: [jdt-dev] Performance of type and constructor completions

[Daniel Megert <daniel_megert@xxxxxxxxxx>]

Hi Marcel

As a start I suggest to read https://bugs.eclipse.org/6930
which contains some discussions regarding constructor proposal performance
and that we tried hard to have better performance. You'll also see that
we even added a content assist timeout due to that feature. Maybe the performance
could be improved, maybe not or maybe at a to high cost. Unfortunately,
fact is, the JDT team will definitely not have time to look into this for
you - at least not until Luna ships. If the performance is a problem for
you, then you will have to dig into the internals and proposes solutions
that we can merge into the product during Mars time frame.

Dani



From:      
 Marcel Bruch <marcel.bruch@xxxxxxxxxxxxxx>
To:      
 jdt-dev@xxxxxxxxxxx
Date:      
 06.03.2014 17:32
Subject:    
   [jdt-dev] Performance
of type and constructor completions
Sent by:    
   jdt-dev-bounces@xxxxxxxxxxx

---

Hi jdt-dev,

we get a couple of complains that Subwords Completion is slowing down content
assist. There is actually a significant slowdown when it comes to type
and constructor completions. 

To make Subwords work (for type and constructor completions), we trigger
content assist a second time after the first char of the prefix string
- if there was one. The problem we experience then is, that triggering
code completion on very short prefixes is extremely slow (compared to triggering
completion with a prefix of 2,3 or even more letters) for types and constructors.

With that email I’d like to start a discussion whether it’s possible
for JDT to find ways to significantly improve the speed of content assist
for type and constructor completions. Would it be possible to improve performance?
If so, how - and how much would it cost (in terms of time)?

Our ultimate goal would be to create completion proposals even without
*any* prefix for type and constructor completions. But this is currently
not possible with JDT if we want to reuse its cu.codeComplete() methods.

Any ideas are greatly appreciated.

Thanks,
Marcel
_______________________________________________
jdt-dev mailing list
jdt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/jdt-dev