Auto Maintenance: Controls whether persistent store is maintained automatically (i.e. events reaching their TTL, or events which have been purged are cleared from the channel storage file.

Honour Capacity: Whether the channel / queue capacity setting will prevent publishing of any more data once full. If true, the client will get an exception on further publishes (a transactional publish will receive an exception on the commit call, a non transactional publish will receive an asynchronous exception through the nAsyncExceptionHandler). If false the oldest event will be purged to make room for the newest.

Enable Caching: Control the caching algorithm within the server, if you set caching to false, all events will be read from the file store. If true then if server has room in memory, they will be stored in memory and reused.

Cache on Reload: When a server restarts it will scan all file based stores and check for corruption. During this test the default behaviour is to disable caching to conserve memory, however, in some instances it would be better if the server had actually cached the events in memory for fast replay.

Enable Read Buffering: Control the read buffering logic for the store on the server.

Read Buffer Size: If ReadBuffering is enabled then this function sets the size in bytes of the buffer to use.

Sync Each Write: Control whether each write to the store will also call sync on the file system to ensure all data is written to the Disk

Sync Batch Size: Control how often in terms of number of events to sync on the file system to ensure all data is written to the Disk

Sync Batch Time: Control how often in terms of time elapsed to sync on the file system to ensure all data is written to the Disk

Fanout Archive Target: Control whether all events fanned out are written to an archive q