|
|
by Craig Shallahamer Get the book here |
|
|
Craig Shallahamer's Blog
The text below is an except from the book, Oracle Performance Firefighting, written by Craig Shallahamer of OraPub, Inc. Figures and tables are not included on this page, only their reference. To order the book in either print or PDF form, click here. ©2009, 2010 by Craig Shallahamer. This is copyrighted material. Please—Out of respect for those involved in the creation of the book and also for their familes, we ask you to respect the copyright both in intent and deed. Thank you. ------------------------------- As you can see, Oracle source code instrumentation is incredibly valuable and was a major performance analysis breakthrough for Oracle Corporation. Oracle instrumented its code starting with Oracle 7. The beauty of this instrumentation is that Oracle made the information available through the SQL interface. Oracle could have forced us to trace a specific process or processes, and perhaps use an additional command like tkprof to consolidate and format the information. By making the instrumentation details easily available through the performance views, Oracle has encouraged performance analysts and vendors to use the information. I personally believe that Oracle instrumented its code for kernel optimization, not for DBAs or application developers. An obvious clue is the names given to describe the timing, such as db file scattered read to relate non-buffer cache multiblock reads and latch free to signify latch sleep time. No DBA would have come up with names like these! Please—Out of respect for those involved in the creation of the book and also for their familes, we ask you to respect the copyright both in intent and deed. Thank you. |
Know what's important before it's too late!
OraPub's
Performance Training
is like no other...
More Class Pics...
Get student testimonials!