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.
-------------------------------
The touch count reset value when a buffer header is promoted. Consistent read and segment header blocks are exempt.
The touch count reset value when a buffer header crosses from the hot region into the cold region. Decreasing this will make it more difficult for a buffer header to be promoted.
Write lists, commonly called dirty lists or LRU-W lists, are composed entirely of dirty buffer headers. Each of the dirty buffer headers is also in the CBC structure. Oracle has the concept of a working set, which consists of an LRU latch, an LRU chain, and a write list. Each database writer is associated with one or more working sets. Upon instance startup, Oracle will determine the number of working sets and the number of database writers (init.ora db_writer_processes, which has a default of 1), and then set their association. When a database writer writes, it feeds off one of its write lists. Both server processes and database writers move unpopular dirty buffer headers from their LRU chains to their associated write lists. Now let's inject some movement into these facts.
©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.
|