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.
This is an umbrella issue for code-completion improvements planned for promo-E
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.
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.
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).
Code completion doesn't brign all contents (packages and classes) of the package.
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.
closing