Dear Gentlemen, thank You very much to finally having brought this much awaited feature.Build 514 (January 24, 2005):
CPU profiling: own method times (e.g. without time spent in subcalls) are shown in 'Invocation tree'
However, I must now be sure, You still haven't understood how a CPU profiler is used (a question: do You at YourKit ever use CPU profiling yoursevles? -- I mean use, not test...)
To be as precise as necessary, I will now list all bugs present in the actual implementation of the feature. Every single item renders the feature useless, hence the entire profiler (cf. discussion above - read: I still cannot buy or recommend your product).
Buglist:
- Own time appears in the invocation tree. However, Own time is not shown for collapsed items, and uncollapsing all items is an extremely slow and tedious process. An "Uncollapse All" button is missing.
The Own time of a collapsed items is the sum of all hidden Own times and not zero.
Once the invocation tree is uncollapsed, one cannot sort according to Own time (one would have to give up the tree structure, of course).
A method appears multiple times in the tree if called via different chains. It must not, of course, because own time means the sum over ALL invocations.
Any Own time must still include time spent in all FILTERED methods because THEIR own time does never show up elsewhere.
Own times of 15ms or 0ms under Windows should be summarized as 'eps' because the Java-on-Windows clock resolution is too small. It may be usefull to have a native clock or combine several profiles into a single, more accurate, one. But this item is a feature, not a bug.