You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Timothy Bish (Closed) (JIRA)" <ji...@apache.org> on 2011/09/27 16:50:11 UTC

[jira] [Closed] (AMQ-3309) 5.5.0 - kahadb indexing to be reviewed

     [ https://issues.apache.org/jira/browse/AMQ-3309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Timothy Bish closed AMQ-3309.
-----------------------------

       Resolution: Duplicate
    Fix Version/s: 5.6.0

Duplicated by AMQ-3467 which has been resolved.
                
> 5.5.0 - kahadb indexing to be reviewed
> --------------------------------------
>
>                 Key: AMQ-3309
>                 URL: https://issues.apache.org/jira/browse/AMQ-3309
>             Project: ActiveMQ
>          Issue Type: Bug
>          Components: Broker
>    Affects Versions: 5.5.0
>            Reporter: Denis Urusov
>             Fix For: 5.6.0
>
>
> amqpersistence adapter outperforms kahadb by 4X.
> re: http://activemq.2283324.n4.nabble.com/disk-IO-rate-peak-tp3504958p3507749.html
> "There was some recent work on message priority support for durable 
> subs which puts more pressure on the index for each message send. My 
> suspicion is, that is the cause of the slow down. Unfortunately it is 
> not possible to disable priority ordering at the moment. 
> Can you open a jira issue to track this, we should be able to attain 
> parity with the amqPersistenceAdapter for this use case. I will try 
> and get some time over the next few weeks to investigate further. "

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira