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.
According to the report (see URL) and additional measuring done on prj40_prototype build 200305230000, there are two steps in creating a class that are unacceptably slow. Note this is related mainly to the first use of the New wizard. (1) going to the second page of the New wizard (to enter name after choosing template - measured for Main template); this takes almost 4 seconds for the first time (should be max 1 sec, in NB 3.5 this was under 1 sec), subsequent invocation is ok (2) finishing the wizard and opening the file in editor; this took about 6 sec first time (should be max 2 sec, in NB 3.5 this was 2.4 sec), and 1.5 sec when repeated (should be max 1 sec) [build 200305230000, jdk 1.4.1_02, Win2000, PC 733MHz]
See also issue 28959 how the responsiveness was improved in NB 3.5.
Attaching profiling snapshots done in OptimizeIt on build 200305230000 (note creating new class does not work in newer 200305300000).
Created attachment 10522 [details] profiling snapshot of 1st use of "Next" step; "sampler" method
Created attachment 10523 [details] classes loaded during the 1st "Next" step invocation
(1) seems to be the usual first-use heavy class loading & initialization problem - about 700 classes are loaded. This is a bit better in 20030528 build where editor warm-up was partially reimplemented, but editor probably should not be touched at all in this phase... Parsing seems to be involved significantly too. I guess this could be tuned using a reasonable combination of lazy initialization and warm-up techniques.
Created attachment 10524 [details] profiling snapshot of 1st finishing wizard and opening java file; "sampler" profiling method
Created attachment 10525 [details] profiling snapshot of 2nd finishing wizard and opening file; "sampler" profiling method
Created attachment 10526 [details] classes loaded during 1st finish&open
(2) also suffers from class loading & initialization in the first use, but there is also significant time spent in tempalte instantiation even for the second time. There could be also some inefficiency in updating the UI (explorer nodes, opening editor).
The projects prototype has been canceled. For more details see http://www.netbeans.org/servlets/ReadMsg?msgId=619519&listName=nbdiscuss