This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 51714 - Improve code-completion performance/responsiveness for promo-E
Summary: Improve code-completion performance/responsiveness for promo-E
Status: CLOSED FIXED
Alias: None
Product: ide
Classification: Unclassified
Component: Performance (show other bugs)
Version: 3.x
Hardware: All All
: P1 blocker (vote)
Assignee: _ ttran
URL:
Keywords: PERFORMANCE
Depends on: 43284 47443 52006 52013 55832
Blocks:
  Show dependency tree
 
Reported: 2004-11-22 13:05 UTC by Antonin Nebuzelsky
Modified: 2011-05-25 11:36 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Antonin Nebuzelsky 2004-11-22 13:05:38 UTC
This is an umbrella issue for code-completion
improvements planned for promo-E
Comment 1 Antonin Nebuzelsky 2005-02-22 13:38:45 UTC
VOC - users were complaining in performance survey very much about
code-completion:

* Code completion is slowed down, I guess it's the lookup of local
variables that slows it down (that's new).I don't need it, I rather
use ctrl-K or L.
* Code completion popups in Editor window are much slower than I
experienced in 3.6. Especially HTML/JSP popups. 
* Autocomplete popup is very slow, even once it has appeared. It just
can't keep up with the typing - even if I type slowly I need to wait
for the autocomplete window to catch up. 
* The code completion and display of JavaDoc is the most bothersome
yet the most useful.
* CodeCompletition 
* Code suggest will occasionally just hang the whole application for
several seconds (10-20).
* Code-completion needs to be faster.
* codecompletion
* Pop up code completion can be the slowest.
* Code completion could be improved
* The code completion is a little slow.
* Code completion is too slow
* Netbeans runs acceptably fast on a 2.5ghz/768mb RAM Window machine
(excepting code completion which pretty much sucks everywhere :-).
* code completion of packages, clases, methods, etc. of java code in a
JSP file is tooos slow. The same completion on a .java file works very
well, so the problem is ONLY with .jsp files.
* Code completion is the biggist problem.
* Code auto completion seems faster in netbeans 3.6 than in netbeans 4.0.
* Code completion popup is **painfully** slow.
* Code Completion
* Sometimes code completion is an annoyance because NetBeans does not
respon until the javadoc window is displayed and the content is rendered.
Comment 2 Martin Matula 2005-02-22 13:58:10 UTC
There are several references to slow *JSP* completion. It is possible
that a lot of people complain because of that (even when they don't
say it explicitly). I guess the JSP completion is slower because it is
done a little differently (using bridge to JC-classes) and maybe its
performance could be improved.
Comment 3 _ rkubacki 2005-02-28 09:01:06 UTC
I agree that JSP code completion deserves special attention. There are
more reasons why it can be slow as it has more complex context
(HTML/XML/JSP secific tag or directives, own tag libraries, Java
scriplets).
Comment 4 mabasara 2005-03-12 09:37:17 UTC
Code completion doesn't brign all contents (packages and classes) of the package. 
Comment 5 Antonin Nebuzelsky 2005-08-30 12:16:06 UTC
Closing this umbrella promo-E issue as fixed. Some parts of the problem were
really fixed in E. Will be tracked from start again in F.
Comment 6 Marian Mirilovic 2005-12-14 16:25:54 UTC
closing