You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@activemq.apache.org by "Christian Posta (JIRA)" <ji...@apache.org> on 2015/02/20 17:32:12 UTC

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

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

Christian Posta commented on AMQ-5603:
--------------------------------------

work started here https://github.com/christian-posta/activemq/commit/db1335d5883a4943c7d1cb6cef21d534676cafbb#diff-10aa392dba6f176b982ddd0229c2c407R118

> 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)