I’ve published a new utility to generate a trace file event timeline. It’s available on appsdba.com here. I’ve also updated the original interval resource profiler with the same code as the event profiler utility so that it displays CPU events separated by PARSE, EXEC and FETCH with full recursive accounting. The previous version grouped all CPU time into one “event” called “CPU Service” and only distinguished between non-recursive (e.g. dep=0) and recursive (e.g. dep>0) time. The new utility also sorts events, which my original attempt did not, but so far I have not seen a significant difference in the recursive time accounting. The event sort has changed the look of the graphs slightly from the originals, so comparisons are a little more difficult. The time accounting is correct so far, so it looks like this version is accurate. I will be publishing a new utility shortly that can generate the “execution tree” that I showed in my previous article “Trace Event Timeline -  Recursive, Non-Recursive and Exclusive Time“. This utility makes it easier to reconcile time to insure proper time accounting.

As for the graph comparison? Here’s the new view of the same graph that I showed in Part 3 of this trace event timeline series.