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 27783 - Explicit invocation of code completion must be fast
Summary: Explicit invocation of code completion must be fast
Status: VERIFIED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: All All
: P2 blocker (vote)
Assignee: issues@editor
URL: http://performance.netbeans.org/respo...
Keywords: PERFORMANCE
Depends on: 28393
Blocks: 26581 27785 34161
  Show dependency tree
 
Reported: 2002-10-03 16:04 UTC by _ rkubacki
Modified: 2007-11-05 13:42 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ rkubacki 2002-10-03 16:04:00 UTC
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.
Comment 1 _ pkuzel 2002-10-25 18:56:27 UTC
Automatic completion check must not affect issue 27785.
Comment 2 _ pkuzel 2002-10-25 18:57:49 UTC
Automatic completion check must not affect issue 27785.
Comment 3 _ pkuzel 2002-11-01 16:21:37 UTC
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). 
Comment 4 _ pkuzel 2002-11-05 22:05:02 UTC
branch_13768 contains patch that shows "Please  
wait" result if explicit code completion  
request can not be displayed until 100ms. 
Comment 5 _ pkuzel 2002-11-14 15:16:52 UTC
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.
Comment 6 Marian Mirilovic 2002-11-22 09:46:27 UTC
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
Comment 7 _ pkuzel 2003-01-28 11:21:11 UTC
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.
Comment 8 Tomas Pavek 2003-01-28 17:13:33 UTC
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...
Comment 9 Martin Roskanin 2003-01-29 10:05:20 UTC
I think "Please wait..." solves this issue. 
As for the slow character displaying, there is already the issue
#27785 created for that.
Comment 10 Marian Mirilovic 2003-02-04 18:09:57 UTC
I agree, please wait solve responsibility (not performance) , but it
looks much better.