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.
Beginning of action: User types a character that makes code completion possible Initial Feedback: Menu appears (populated or unpopulated) Maximum time allowed: 100 ms For example first invocation of HTML completion is noticeably slow.
Automatic completion check must not affect issue 27785.
Consultation with HIE showed that auto-popup completion logic should be opposite. Automatic completion must not disturb user for AUTO_COMPLETION_DELAY period (default 500ms) then it can appear in any time because it is only speculative hint. You probably ment explicit code completion request (ctrl+space) that must provide fast feedback (till 100ms).
branch_13768 contains patch that shows "Please wait" result if explicit code completion request can not be displayed until 100ms.
Analysis of Java completion databases scalability can help. I will try to determine impact of using many JCC databases and JavaDoc mount points. On the other hand I hope that Java editor will work only with databases valid in current project context. It'll improve scalability. Thanks to Emanuel for pointing this out.
Marian's measurement (time in milliseconds): conditions: - SUN UltraSparc60 / 512 MB RAM / Solaris 5.8 / CDE - JDK1.4.1(01) - [nb_dev](200211140100) , MDI - mounted sampledir bring up code completion popup: cursor on position "Sys<>" 507 99 70 javadoc arise 364 353 Test cases described on page : http://performance.netbeans.org/qa/TestSuites.html#code_completion_in_java_file
I have forgoten to mention that "Please wait" result patch (if explicit code completion request can not be displayed until 100ms) is already applied. Unfortunatelly it does not address very first usage when completion framework class loading can take more than 100ms.
For me, the "Please wait" message works quite good, also for the first use... Another thing is strange with the first use - it takes one or two seconds the editor to wake up and start displaying characters, so if I repeat the Marian's case - typing "Sys" and pressing Ctrl+Space, I wait longer for "Sys" to appear than "Please wait" message for code completion...
I think "Please wait..." solves this issue. As for the slow character displaying, there is already the issue #27785 created for that.
I agree, please wait solve responsibility (not performance) , but it looks much better.