[APLO-20] Optimize session acked durable subs by using a shared durable queue.

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Won't Do
• Fix Version/s: 1.8
• Component/s: apollo-bdb, apollo-broker, apollo-leveldb
• Assignee: Unassigned
• Reporter: Hiram R. Chirino
• Created: 23/May/11 13:49
• Updated: 06/Apr/22 19:16
• Resolved: 06/Apr/22 19:16

Description

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.

Issue Links

• is related to: APLO-251 Share a single queue for all consumers on topic configured with slow_consumer_policy="queue"