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.
-------------------------------
3 Speaking as a buffer, it's my goal to remain in the cache. Being a popular buffer will increase my likelihood of remaining in the cache. And being a popular dirty buffer, well, that carries a certain mystique.
4 My sources related to the touch-count algorithm were an Internet posting by Steve Adams of Ixora, an internal Oracle source, and hours and hours of testing and experimenting. That was enough to allow me to perform my research and publish a paper entitled All About Oracle's Touch-Count Algorithm in 2001. From what I can tell, James Morle made the first public hint of the touch-count algorithm in his 2000 book, Scaling Oracle8i (Addison-Wesley).
5 Always remember that when we change an instance parameter, it is truly only a suggestion. If our change places Oracle in an impossible situation or Oracle deems the change inappropriate in any way, Oracle may simply ignore our suggestion or choose a value that is close to our suggestion and acceptable to Oracle.
©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.
|