is a critical configuration
for maximizing database and server performance, and it is vital for ensuring
data integrity and implementing a reliable backup and recovery architecture.
When transaction logging is enabled
the server writes sequentially to a binary file instead of randomly to
nonsequential parts of a database. Because this involves far less movement
for disk heads, the resulting I/O is much faster. Additionally, Domino
defers writing the logged transactions to disk during periods of heavy
activity. This both conserves resources when Domino is most busy and optimizes
system I/O by batching disk writes such that the operating system spends
less time in kernel mode, leaving more time for applications like Domino.
Careful planning and configuration is required when enabling transaction
logging so that these performance gains will be realized. In particular,
the disk subsystem architecture must be configured with transaction logging
in mind. To achieve the full benefits discussed here, transaction logging
must be configured to use a dedicated disk and disk controller.