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.
'Go To Class' performance seems to be degraded in 4.1 final release. If class name is typed 'Class Name' field in the 'Go to Class' dialog box then it takes lot of time to filter the classes beginning with the typed text especially when there are lot of classes beginning with similar text and source size is large (>100M). This search used to happen quickly in netbeans 3.6 , 4.0 and 4.1 Beta but in 4.1 final release performace of this search seems to be degraded. My source if in clearcase dynamic view and I am using this functionality to open the source files rather than clicking the source tree from Files or Project Window which takes some time. Also, another observation is that if wrong text is typed in the 'Class Name' field and the ESC is pressed then it appears that netbeans does not stops the searching ( observed from task manager ->process CPU usage) . It appeans that if ALT+SHIFT+O is pressed again and correct text is typed then this search executes only after earlier search is completed which is actually cancelled. If ALT+SHIFT+O is pressed after placing cursor in class name in the source then it quickly returns the matching class. This performance issue appears only if text is typed in the 'Class Name' field
Performance team, can you help us with this issue? Thanks.
I'd like to but it may take a while. Still have a bunch of other items on my to do list. Anyway it looks to me that canceling works well in 5.0 builds (there is a better way to cancel running task in 5.0 and we are probably utilizing this).
Could the construction of tooltips be a part of the problem? AFAIK tooltips for the Go To Class items where added later than in 4.0, maybe that it was sometime before the 4.1 final. See my issue 61774 which was fixed in trunk lately, so the problem should not appear in 5.0 beta.
Performance in 5.0 Beta is reasonably good though 4.0 performance of this operation was much better.
I verified that the tooltips are really part of the problem for NB 4.1 final (in comparison to NB 4.1 beta) - see the fix of an issue 49737 which was introduced after 4.1 beta. This is now eliminated with the fix of issue 61774. I scanned other issues fixed after 4.1 beta and before 4.1 final and found the following 2 related to functionality and performance of Go To Class dialog: issue 54312 - Debugger restricts contents of Go To Class dialog issue 53406 - Fast open dialog opening sometimes very slow None of these two, I think, can have effect on the behavior you describe. So, sorry, I don't know what else could cause the regression and thus could be improved. Editor/Javacore teams, please, try to find what you changed between 4.1 beta and final in your infrastructures what could have an effect on Go To Class performance. Thanks.
Currently we are not aware about other things that we could improve regarding this. The most serious was likely issue 61774 which is now fixed.