Please use the Apache issue tracking system for new NetBeans issues ( !!
Bug 80723 - Performance of popup menus
Performance of popup menus
Product: ide
Classification: Unclassified
Component: Performance
All All
: P3 (vote)
Assigned To: issues@performance
Depends on: 65370 73810 73814 73816 73818 73820 73821 77909 77963
  Show dependency treegraph
Reported: 2006-07-20 14:50 UTC by Petr Jiricka
Modified: 2011-05-25 11:37 UTC (History)
3 users (show)

See Also:
Issue Type: DEFECT


Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2006-07-20 14:50:10 UTC
Popup menu performance is not within the performance criteria for various
objects. Based on Radim's evaluation, the improvement needs to be done mostly in
the popup menu infrastructure; the individual DataNode implementations can not
really do much:

Subject: Update on performance bugs in J2EE (5.5)
Date: Thu, 15 Jun 2006 16:15:08 +0200
From: Radim <xxxxxx@Sun.COM>


last couple of days I was trying to found something what can help us to 
make popups on various nodes faster. There was struggling with analyzer 
and with our profiler too (#77839).

I did not find any low hanging fruit here. Couple of observations include:

- some tuning in SFS that Petr N. can do
- change of node selection is more expensive than I'd like to see. For 
example #77963, some updates performed by debugger can be perhaps 
optimized too.
- what I saw in profiler recalled me that sometimes we use CookieAction 
although subclassing NodeAction is enough
- classloading is apparently a problem. For example we can simplify some 
things in xml that are useless now (#77909). Init of SystemAction is 
also a bit slower that simple Swing action

These are not big wins so I will continue next week and will look into 
editor opening too.

Thus, I am changing the object-specific issues to TASKs and filing this as a
DEFECT to track them.
Comment 1 Petr Nejedly 2006-07-21 10:33:10 UTC
None of the points from the Radim's evaluation suggest the nodes infrastructure
is the problem.
- SFS is core (I have already done some improvements there).
- Node selection change is slowed down by individual listeners, mostly module
- Actions again, lookup usage is expensive when not necessary

Anyway, I'll try to profile the popup menus again and look at individual time
Comment 2 Petr Jiricka 2006-07-21 13:28:15 UTC
> None of the points from the Radim's evaluation suggest the nodes infrastructure
> is the problem.

Ok, point taken, I am not sure where exactly the improvements can be gained.
Thanks for looking at this.
Comment 3 _ hair 2007-03-05 13:01:03 UTC
Try selecting 30+ projects and then trying to open the popup menu.
It takes foooooooooreeeeeeeeeeeeeeeeeeeever.
I mean I can make myself a cup of coffee in both the time it takes to select the
projects, and the time it takes to bring up the popup menu.
Also try deselecting just one project (with the control key) out of the selected

These operations in the IDE are really not usable.
Comment 4 Petr Nejedly 2007-11-01 11:50:50 UTC
What times do you see currently.
I was about to profile it, but for me, while the times were out of UI responsiveness boundaries, the IDE was still usable
I tried 23 (Editor module and all its dependencies) NBM projects  (which are generally considered quite slow) and both
selecting them and invoking popup was between 1-2s.
Comment 5 Antonin Nebuzelsky 2008-02-08 15:04:59 UTC
Reassigning to new module owner Tomas Holy.
Comment 6 Marian Mirilovic 2011-05-25 11:19:18 UTC
too old, no plans to fix this issue

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo