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.
When trying to find ~6000 usages of class, it takes minutes. Here are data for comparison (project internally available at http://jupiter.czech.sun.com/wiki/view/NbQE/TestingProjects, Java Free Form). Look for usages of DBObject class: 5.5 - 75-95s - Mx256m 6.5.1 - OOME, with Mx increased to 768M 50-65s 6.7.1 - 140-175s, with Mx increased to 768M 85-93s trunk - 155-170s - default -Mx, in this case ~500M. (with Mx256m OutOfMemoryError), with Mx 768M 75-80s eclipse galileo - 12-15s
ohh, sorry, wrong issue
There are involved several things. I will file separate issues for them and leave this issue as an umbrella. Strange is the memory consumption at first look. Lack of memory slows down javac significantly. The thread dump analyzes shows that there are many instances (~900000) of PositionBounds and other classes related to Document. See issue 171331 for more.
Another place significantly slowing down the find usages seems to be WhereUsedElement.create which starts the java lexer (issue 171652).
In case of huge results (> 5000 occurrences) it is pretty slow to expand all nodes or switch physical/logical view and it may even run out of memory (issue 171657).
The last measure of find class usages shows 45-48s with default -Mx on the tested project. It is up to 4x faster in comparison with previous releases. The node expansion runs 10x faster and the memory is not exhausted. The most time is consumed by javac attributing now. Faster times would be possible only with rewritten refactoring infrastructure (lazy nodes, perform just parsing not attributing or .class file inspection) which is not doable for 6.8. I consider this as fixed for NB 6.8.