Chapter 35. Tuning Persistence
Put the message journal on its own physical volume.
One of the advantages of an append-only journal is that disk head movement is minimized. This advantage is lost if the disk is shared. When multiple processes, such as a transaction coordinator, databases, and other journals, read and write from the same disk, performance is impacted because the disk head must skip around between different files. If you are using paging or large messages, make sure they are also put on separate volumes.
journal-min-filesparameter to the number of files that fits your average sustainable rate. If you frequently see new files being created on the journal data directory, meaning a lot data is being persisted, you need to increase the minimal number of files. This allows the journal to reuse, rather than create, new data files.
Optimize the journal file size.
The journal file size must be aligned to the capacity of a cylinder on the disk. The default value of
10MBshould be enough on most systems.
For Linux operating systems, keep your journal type as
AIOscales better than Java
journal-buffer-timeoutvalue results in increased throughput at the expense of latency.
If you are using
AIO, you might be able improve performance by increasing the
journal-max-ioparameter value. Do not change this value if you are using