transaction logging

Transaction logging appeared to have a small but significant effect on overall performance and for the two major transaction types.

If transaction logging is used for backups, use this switch only before the full backup schedule (once a week).

While transaction logging provides substantial benefits, it has a definite cost in terms of additional CPU consumption.

We did not enable Lotus Domino transaction logging for this comparison.

The first area of interest was the benefit vs. performance cost of transaction logging.

Before we get into the numbers, we'll start with a general overview of transaction logging and its benefits.

With transaction logging enabled, the system captures database changes and writes them sequentially to the transaction log.

Transaction logging writes all transactions out to a separate group of files.

In this article, we'll take a look at a performance analysis of Domino transaction logging on Windows NT.

A transaction logging method in which the log is always written prior to the data .

With our test configuration, we found an across-the-board improvement in performance when turning on transaction logging.

With transaction logging enabled, the system captures database changes and writes them to the transaction log.

Editor's note: We're excited to have this article on transaction logging, which we implemented on the Notes. net site.

Transaction logging improves overall Domino server transaction throughput, which potentially allows the same server to support more users.

The speed of a transaction logging device becomes more of a factor under heavy view or folder activities.

Reducing mail file size improves performance of view indexing, compact, backup and restore, and transaction logging.

With transaction logging, Domino posts transactions (or writes) to a series of log files prior to allowing any updates to the database.

Transaction logging also has system-level benefits as well.

At a minimum, implement circular transaction logging for greater data integrity and faster restarts.

For more information about transaction logging, see Understanding Transaction Logging.

Finally, transaction logging also means the end of those long Fixup sessions!

This topic provides a detailed description about how transaction logging works, including circular logging.

The resource utilization went up slightly on the standby server after transaction logging was enabled on both servers.

Persistence is achieved using built-in checkpoint and transaction logging mechanisms.

We also determined that transaction logging enhanced disk utilization on the clustered server.

These tasks will also see some savings from using zSeries hardware compression for transaction logging.

We recommend transaction logging for high availability and failure recovery.

Transaction logging will, of course, improve reliability and restart time.

If you're using transaction logging, you must account for the extra cycles needed to run it.

Notice that with transaction logging turned on, the average transactions per minute increased by about 16 percent.

Transaction logging was enabled, and used archival logging.

Allocate a space for the transaction logging directory.

These results are from a single Domino partition, which is not using transaction logging, except where noted.

Learn how to increase performance using transaction logging, multiple mail. boxes, and multiple disk drive controllers.

Separate volumes were allocated for the Lotus Domino execution, Notes data, Domino Directory, mailbox 1 to 4, and transaction logging.

All tests are run with transaction logging enabled, and run using circular mode.

Transaction logging in Domino R5 adds a dimension that streamlines all database transactions.

Transaction logging is a capability that has a good track record.

Now, let's look at the relative impact of turning on Domino transaction logging.

We ran transaction logging enabled, with hardware compression data instead of LZ1 software.

I have a few comments about transaction logging in R5, partitioning, and clustering, and how they affect performance.

And we ran zSeries hardware compression for transaction logging (a feature of Domino 7).

Transaction logging was set up on a separate three-disk array of 200 GB, RAID 0.

Database improvements, such as transaction logging and a new on-disk structure (ODS)

Turn on transaction logging -- R5 only (Database)

An introduction to transaction logging: A better solution