[
https://issues.apache.org/jira/browse/AMQ-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15897222#comment-15897222
]
ASF subversion and git services commented on AMQ-6377:
------------------------------------------------------
Commit 0d824a8e6832419cb952ef503504c5296b069ad9 in activemq's branch
refs/heads/master from [~cshannon]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=0d824a8 ]
AMQ-6377: Storing JournalSyncStrategy as an enum
Switching MessageDatabase to store JournalSyncStrategy as its enum value
instead of String to avoid the performance penalty of comparing Strings
everytime isEnableJournalDiskSyncs() is called which currently happens
on every write.
> Introduce a periodic disk sync mode for KahaDB journal
> ------------------------------------------------------
>
> Key: AMQ-6377
> URL: https://issues.apache.org/jira/browse/AMQ-6377
> Project: ActiveMQ
> Issue Type: New Feature
> Components: Broker, KahaDB
> Affects Versions: 5.13.4
> Reporter: Christopher L. Shannon
> Assignee: Christopher L. Shannon
> Fix For: 5.14.0
>
>
> KahaDB has two modes for journal disk syncs, either always sync for each
> write or never sync. I'm proposing that we add a third option, a period disk
> sync.
> The intended behavior of this would be to run a task in the file appender
> that would sync the file (if necessary) at some periodic interval (such as
> every 500 ms, or 1 second, etc) instead of every write. The file would also
> be synced on close (on file rollover or shutdown)
> In my testing, syncing every 1 second has been proven to be nearly
> indistinguishable performance as never disk syncing but is a safer option as
> you insure that a sync is performed at least once per interval.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
