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.
Seeing as a lot of users I talk to complain about Netbeans' overall performance I propose selecting 2-3 most-frequently-used tasks (per module!) and document where cpu usage is going. What I mean per module is that we should document 2-3 typical tasks per editor tasks, filesystem tasks, CVS tasks, etc... and work to streamline in all fronts. Is this doable?
Since the time of NB 3.4 a lot of changes have been made in the performance area. I hope it is much better now. I think we actually did it the way you were suggested...