Re: [SwiftMQ4.6.0] How to configure the interval for running force-sync
Wednesday, March 31, 2004 03:53 AM
The log manager works asynchronous in a separate thread. While it writes log records to the transaction log, other threads (store transactions) can write into the log manager's queue which then takes these bunch of records to write it to the tx log. This is meant with log manager interval. The number of log records processed in such an interval is determined by the number of transactions in parallel. It is not configurable in your release. SwiftMQ 5.0.0 introduces an attribute "group commit delay" which delays the log manager further to have a chance to get even more log records per interval. This delay is only useful if you have a very high rate of parallel transactions. It is not useful if you have only a single transaction because this tx would then be delayed.
If you have a hig tx rate, you should increase the jms.session thread pool setting to have more threads committing in parallel.
The force-sync attribute ensures that a write to the tx log is finished with a disk sync. A checkpoint is performed anyway if the tx log reaches its max size.