[
https://issues.apache.org/jira/browse/APLO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hiram Chirino updated APLO-20:
------------------------------
Fix Version/s: (was: 1.7)
1.8
> 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-leveldb
> Reporter: Hiram Chirino
> Fix For: 1.8
>
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
