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.
JavaNode constructor spends most of the time (~1000ms for 120 files in a folder) inside FileBuiltQuery.getStatus() Status resolution (which is both processing and I/O expensive) should be performed later, once the folder is rendered, at best. Note that the threading is not that simple here, there are already few threads involved in folder expand: FolderRecognizer, which converts FileObjects into DataObjects FolderChildren_Refresh, which creates the nodes for the DataObjects (this is where this slowdown happens) AWT thread which renders the nodes later. Also note that it _might_ cause some problems to fire a lot of status changes one-by-one, so some testing of this scenario might be necessary.
Checking in org/netbeans/modules/java/JavaNode.java; /cvs/java/source/src/org/netbeans/modules/java/JavaNode.java,v <-- JavaNode.java new revision: 1.12; previous revision: 1.11 done
Looks much better now. At least in the JavaNode ctor....