[jira] [Comment Edited] (AMQ-6377) Introduce a periodic disk sync mode for KahaDB journal

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

    [ https://issues.apache.org/jira/browse/AMQ-6377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15397451#comment-15397451 ] 

Gary Tully edited comment on AMQ-6377 at 7/28/16 12:01 PM:
-----------------------------------------------------------

yep. trace is sensible, and you can track the location if you want to avoid the fsync when there is no data.
For the rotation, doing an fsync followed by another fsync should be fast. as in the second call has nothing to do.



was (Author: gtully):
yep.
For the rotation, doing an fsync followed by another fsync should be fast. as in the second call has nothing to do.


> 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.4#6332)