This topic has not yet been written. The content below is from the topic description.
46.1. Tuning persistence Put the message journal on its own physical volume. If the disk is shared with other processes e.g. transaction co-ordinator, database or other journals which are also reading and writing from it, then this may greatly reduce performance since the disk head may be skipping all over the place between the different files. One of the advantages of an append only journal is that disk head movement is minimised - this advantage is destroyed if the disk is shared. If you're using paging or large messages make sure they're ideally put on separate volumes too. Minimum number of journal files. Set journal-min-files to a number of files that would fit your average sustainable rate. If you see new files being created on the journal data directory too often, i.e. lots of data is being persisted, you need to increase the minimal number of files, this way the journal would reuse more files instead of creating new data files. Journal file size. The journal file size should be aligned to the capacity of a cylinder on the disk. The default value 10MiB should be enough on most systems. Use AIO journal. If using Linux, try to keep your journal type as AIO. AIO will scale better than Java NIO. Tune journal-buffer-timeout. The timeout can be increased to increase throughput at the expense of latency. If you're running AIO you might be able to get some better performance by increasing journal-max-io. DO NOT change this parameter if you are running NIO.