|
There will be cases where both methods will be result in coarse aggregation. Not only can SQL*Net message from client have a long duration but so can parse, exec, and fetch calls. But it is probably true that one would more often see long SQL*Net message from client durations.
To attribute CPU consumption for, say, a fetch call to multiple subintervals requires assumptions I'm not willing to make.
It assumes time not spent in an event (e.g., db file sequential read) is time spent on the CPU. In other words it assumes that all of the RDBMS is properly instrumented.
It assumes measurement intrusion is zero, particularly writes to the trace file.
It assumes the ending time of an event is known, which is true only for 11g onwards.
|
Favoured: 0
Forum
