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.
Feedback from user: I still have the same problem in Netbeans 5.5.1: I am trying to optimize a web application that runs in a number of worker threads and that makes calls to back-end servers such as data base or EJB servers. The following feature would help a lot: A Call Tree view that shows an aggregate over all the worker threads in my server. This would give me a chance to find the methods that consume the most time by top-down opening the call tree. As it is, this deficiency conspire to make it difficult to find the methods that actually take the most total time: the Call Tree view is spread out over many threads that I must inspect individually to locate the worst method. Apart from this, I found the profiler easy to work with (especially compared to Eclipse TPTP, which I have used before and which insists on recording every single function call instead of an aggregate).
Isn't it a duplicate of Issue 55221?
You're right. It's a duplicate *** This issue has been marked as a duplicate of 55221 ***
Verified duplicate