activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hiram Chirino (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-20) Optimize session acked durable subs by using a shared durable queue.
Date Sun, 28 Aug 2011 10:27:37 GMT

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

Hiram Chirino commented on APLO-20:
-----------------------------------

This should now be implementable since message stores now support storing key-value pairs.
 Each shared dest would store the following key values: 

queue_id->List(dsub_ids)
(queue_id,dsub_id)->queue_seq_id

> Optimize session acked durable subs by using a shared durable queue.
> --------------------------------------------------------------------
>
>                 Key: APLO-20
>                 URL: https://issues.apache.org/jira/browse/APLO-20
>             Project: ActiveMQ Apollo
>          Issue Type: New Feature
>          Components: apollo-bdb, apollo-broker, apollo-cassandra, apollo-jdbm2
>            Reporter: Hiram Chirino
>             Fix For: 1.1
>
>
> Right now every durable sub gets assigned a new queue.  This is only needed to support
out of order acking from the subscription.  If the consumer is doing in order acking like
the JMS API forces, then you can get better performance by using a shared queue /w browsers
but track ack positions using a simple map/index.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message