Jess Holle wrote to nbusers:
I have a project with ~1650 known packages
overall, around ~1450 of which are represented in
the source directory (around 28,000 classes
totaling over 100MB when compiled).

It takes the New / Java Class wizard several
*minutes* to come up -- apparently because it
insists on filling out a drop down containing a
list of all known packages.  It apparently does
not cache this either as it takes just as long the
second, third, etc, time.

Is there any way to turn feature off or get it to
perform reasonably?  [The source package node in
the project view is bad enough, but it is easy to
avoid, the result is cached, and there is a
workaround preference as I recall.]

The fact that New / Java Class is so much worse
and that the source package node was pretty fast
(i.e. apparently pre-cached) after New / Java
Class makes me tend to think that the issue may
largely be one-at-a-time addition to a JComboBox
or some such.  On the other hand, NB4's CPU
consumption goes through the roof and slows down
my whole machine upon New / Java Class, so there
may be more going on here.  I did not take time to
do a thread dump, monitor in jconsole, or any such.

Is this a known issue?  Is there a fix or
configuration setting workaround?  If not, I can
use New / Empty File instead, but that's a rather
awkward workaround to have to suggest to all other
developers in our organization and should be
fixed!  [Even for a smaller project this should be
queries on request via an extra action -- not as
part of bringing up the wizard by default!]