You were brought to this page based on an internet search
and as a free service to Oracle DBAs.
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.
PleaseOut 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.
-------------------------------
* Service time is based on CPU time consumed for each user call and is sampled from the v$sys_time_model view.
* Queue time is based on the v$latch view's time_waited column (but v$system_event could have been used, as the values in these two views are consistently within a tenth of a second).
Figure 3-9. Latching acquisition performance data gathered from a real Oracle system, not based on a model. Notice that Oracle's default latching spin and sleep algorithm actually decreases latch acquisition response time per user call until the CPU subsystem becomes saturated. The test was run on a single four-CPU core Linux Oracle 10g Release 2 system.
©2009, 2010 by Craig Shallahamer. This is copyrighted material.
PleaseOut 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.
|