Internal code changes= additional features=fine grained (event) reporting?
Best Regards,
K Gopalakrishnan
Bangalore, INDIA
- Original Message -
To: "Multiple recipients of list ORACLE-L" <[EMAIL PROTECTED]>
Sent: Thursday, May 16, 2002 9:13 PM
> Has anyone noticed that the number of e
Isn't that something to do with 9i being able to report wait times in
nanoseconds instead of (milliseconds? or microseconds?) in previous versions
??
Raj
__
Rajendra Jamadagni MIS, ESPN Inc.
Rajendra dot Jamadagni at ESPN dot com
An
Not exactly. The granularity of capturing times increased in 9i, but as
Gopal implied, there are just a lot more wait events in 9i as compared to
the previous releases.
Check this link out to see what new events were introduced in 9i :
http://www.oraperf.com/reference.html and click on Wait Even
Raj:
Oracle9i gives timing information in Micro Seconds. Not Nano Seconds
though modern CPUs clocks ticks in nano seconds.
The older versions (8i and below) give timing info in Centi Seconds
(1/100th of a second) .
Best Regards,
K Gopalakrishnan
Bangalore, INDIA
- Original Message -
T
You might notice more total event completions in 9i because there are
about 50% more segments of kernel code that are instrumented in 9i than
there were in 8i (~200 events in 8i, ~300 in 9i).
Clock granularity is 0.01 in 8i, so events that complete in the same
0.01-sec quantum as they began will
There is microsecond granularity in some of the columns, but not all platforms
support microsecond timing.
So some of these are centi seconds multipled by 1. There are ofcourse
exceptions (like Compaq Alpha, that suppports msec clocks).
There are more wait events in Oracle9i but the top wait
