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.
-------------------------------
As you might expect, the general approach is to increment a counter every time a buffer header is touched. The more popular buffer headers will have a higher touch count and are deemed more popular, and therefore should remain in the buffer cache. While this is generally true, how it is implemented is quite different. Figure 6-18 shows a diagram of the touch-count algorithm.
Figure 6-18. Oracle's touch-count algorithm determines buffer header popularity based on the number of times it is touched. Notice the FTS window concept is no longer necessary and has been removed.
There are three key touch-count algorithm aspects: midpoint insertion, touch count incrementation, and buffer promotion. The following sections look at each of these aspects.
©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.
|