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

Christian Posta edited comment on AMQ-5578 at 2/19/15 11:37 PM:
----------------------------------------------------------------

one more commit:

https://github.com/apache/activemq/commit/023b2ac04501a97452eb8a23b6024fd336cb6cf6

added unit tests, logging, and removed the preallocated batch stuff which snuck 
in with the previous commit (rebased off wrong branch!). 

should be good to go now.


was (Author: ceposta):
one more commit:

https://github.com/apache/activemq/commit/45e59e6e839ae89ffc099d32a4180ee307543aae

added unit tests, logging, and removed the preallocated batch stuff which snuck 
in with the previous commit (rebased off wrong branch!). 

should be good to go now.

> preallocate journal files
> -------------------------
>
>                 Key: AMQ-5578
>                 URL: https://issues.apache.org/jira/browse/AMQ-5578
>             Project: ActiveMQ
>          Issue Type: Improvement
>          Components: Message Store
>    Affects Versions: 5.11.0
>            Reporter: Gary Tully
>            Assignee: Gary Tully
>              Labels: journal, kahaDB, perfomance
>
> Our journals are append only, however we use the size to track journal 
> rollover on recovery and replay. We can improve performance if we never 
> update the size on disk and preallocate on creation.
> Rework journal logic to ensure size is never updated. This will allow the 
> configuration option from https://issues.apache.org/jira/browse/AMQ-4947 to 
> be the default.



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

Reply via email to