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.
-------------------------------
I am commonly asked why I don't look at the pages swapped in and only the pages swapped out. Well, if there are pages being swapped in, there must have been pages swapped out. And if pages have been swapped out, there is a good chance they will eventually be paged back in.
Figure 4-15. A vmstat report on a very active four-CPU core database server. The so column represents the number of pages swapped out per second during the reporting interval. As in this sample, we want to this nearly always to be zero.
Performance analysts know that if an Oracle server process (and, God forbid, a background process) has some of its memory pages swapped out, response time for that process will be negatively impacted if the pages are swapped back in. And let's not forget the pages were swapped out because another active process requested memory and the operating system could not immediately provide the memory.
©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.
|