Re: [dtrace-discuss] DTraceToolkit bug in how inclusive times are calculated

2008-02-06 Thread Brendan Gregg - Sun Microsystems
G'Day, On Mon, Feb 04, 2008 at 11:40:04PM -0800, Matthieu Chase Heimer wrote: If there is a better place to report this please let me know. This is best. When adding the inclusive method execution time it is required to use the complete method signature. The problem is likely to be present

Re: [dtrace-discuss] DTraceToolkit bug in how inclusive times are calculated

2008-02-06 Thread Matthieu Chase Heimer
Yes - it is expected to have a longer *inclusive* elapsed time. This is one of a number of reasons why understanding inclusive times is difficult. Note that the inclusive time reports delibrately don't include a Total line - since that would add to the confusion. Consider: #

Re: [dtrace-discuss] DTraceToolkit bug in how inclusive times are calculated

2008-02-06 Thread Matthieu Chase Heimer
So I think I'm managed to make an example that is working correctly even for reentrance. It does complicate the script a little bit though. http://www.osdev.org/dtrace/hotspot_extras/j_calltime2.d Top 10 inclusive method elapsed times (us), PID TYPE TOTAL NAME 1683 method

[dtrace-discuss] DTraceToolkit bug in how inclusive times are calculated

2008-02-04 Thread Matthieu Chase Heimer
If there is a better place to report this please let me know. When adding the inclusive method execution time it is required to use the complete method signature. The problem is likely to be present in other scripts but I've verified it in the Java related scripts that calculate inclusive and