[jira] [Resolved] (AMQ-3646) Allow KahaDB to run without disk syncs, higher through put without the jms persistence guarantee

["Gary Tully (Resolved) (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/AMQ-3646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gary Tully resolved AMQ-3646.
-----------------------------

    Resolution: Fixed

fix in http://svn.apache.org/viewvc?rev=1222705&view=rev

A checkpoint won't disk sync when setEnableJournalDiskSyncs=false on kahaDB. Checkpoint and cleanup can be disabled altogether with a period of 0. The broker jmx view {{gc()}} operation will do a persistence adapter checkpoint/cleanup so it is possible to manually force a gc of the store.

                
> Allow KahaDB to run without disk syncs, higher through put without the jms persistence guarantee
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMQ-3646
>                 URL: https://issues.apache.org/jira/browse/AMQ-3646
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>    Affects Versions: 5.5.1
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: buffer, kahaDB, persistence, sync
>             Fix For: 5.6.0
>
>
> When using the broker as a buffer for persistent data, large bursts or additions, periodic batch removes, we want to become disk bound. Waiting for disk syncs causes unnecessary pauses. If the JMS durability guarantee is not needed, it should be possible to execute without disk syncs. Syncing only on shutdown.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira