IBM 000-8697 Manual Do Utilizador

System Architecture

If the timestamp on the page in the buffer pool is equal to or more recent than
the timestamp for the physical log buffer flush, the “before-image” of this
page conceivably could be contained in the physical log buffer. If this is the
case, the physical log buffer must be flushed before the shared-memory
buffer pages are flushed.

Before the tbinit daemon can flush the physical log buffer, it must acquire the
latch for the shared-memory pointer structure and reset the pointer from the
current physical log buffer to the other buffer. After the pointer is reset, the
physical log buffer is flushed.

Next, the daemon process updates the timestamp in shared memory that
describes the most-recent physical log buffer flush. The specific page in the
shared-memory buffer pool that is marked for flushing is flushed. The
number of modified buffers in the queue is compared to the value of

LRU_MIN_DIRTY

. If the number of modified buffers is greater than the value

represented by

LRU_MIN_DIRTY

, another page buffer is marked for flushing.

The timestamp comparison is repeated. If required, the physical log buffer is
flushed again.

When no more buffer flushing is required, the page-cleaner processes
calculate a value that represents a span of time during which the cleaner
processes remain asleep. This value, referred to as snooze time, is based on the
number of pages that the cleaner processes flushed in this last active period.
(Refer to

parameters to improve OnLine performance.)

OnLine provides you with some information about the specific condition
that prompted buffer-flushing activity by defining six types of OnLine writes
and keeping count of how often each write occurs:

■

Sorted write

■

Idle write

■

Foreground write

■

LRU

 write

■

Chunk write

■

Big-buffer write