[jira] [Commented] (AMQ-5603) Consider preallocation of journal files in batch increments

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on AMQ-5603:
------------------------------------------------------

Commit 62bdbb0db5dc4354f0e00fd5259b3db53eb1432d in activemq's branch refs/heads/master from [~gtully]
[ https://git-wip-us.apache.org/repos/asf?p=activemq.git;h=62bdbb0 ]

https://issues.apache.org/jira/browse/AMQ-5603 - add preallocationScope=full_journal_async that will preallocate a journal in advance or use to avoid latency jitter on journal rotation. Added none option to disable preallocation


> Consider preallocation of journal files in batch increments
> -----------------------------------------------------------
>
>                 Key: AMQ-5603
>                 URL: https://issues.apache.org/jira/browse/AMQ-5603
>             Project: ActiveMQ
>          Issue Type: New Feature
>          Components: Message Store
>            Reporter: Christian Posta
>            Priority: Minor
>              Labels: kahaDB, perfomance
>
> Right now (as of ActiveMQ 5.12 release) we preallocate journal files, but the only scope is for entire journal file. The [potential] issue with that is if user configures large journal file sizes, we can end up stalling writes during log rotation because of the allocation process. There are two ways to do the allocation, configurable to do it in userspace, or defer to kernel space, but nevertheless it would be good to avoid this issue altogether by preallocating in small batch sizes regardless of the journal max file size.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)