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.
Profiler 070314 This is customer request to have the ability to sort Call Tree and Hot Spots by Self Time and Time. Currently Self Time is shown as nodes in Call Tree, so user can't sort Call Tree nodes by Self Time. On the contrary Time is not shown in Hot Spots, only Self Time, so user can't sort Hot Spots table by Time.
*** Issue 105519 has been marked as a duplicate of this issue. ***
I just want to point out that having a total time column here should list the total time in this function from *all* code paths. This information is currently impossible to find in the current profiler since the "call tree" pane only lists the total time for one particular code path. The total time from all code paths is one of the most revealing and useful pieces of information that a profiler can provide and it is no where to be seen as far as I can tell in the current profiler (5.5.1).
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, but I could not find it: A Hot Spot view that shows and sorts by total time instead of self time. A method is equally bad whether it consumes time on the local server or in back-end calls (as then it is just another server that is kept busy), and it is therefore the total time consumed by a method that is more relevant than the self time. As it is, this deficiency conspire to make it difficult to find the methods that actually take the most total time. The total time in Hot Spot view looks like it might be easy to add, either as an additional sortable column or as an option instead of the self time. 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).