You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@activemq.apache.org by "Hiram Chirino (JIRA)" <ji...@apache.org> on 2011/05/23 15:49:47 UTC
[jira] [Created] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
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
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
[jira] [Updated] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ 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.3)
1.4
> 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.4
>
>
> 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.
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
[jira] [Commented] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ 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.1)
1.2
> 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.2
>
>
> 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.
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
[jira] [Updated] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (Updated) (JIRA)" <ji...@apache.org>.
[ 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.2)
1.3
> 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.3
>
>
> 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.
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
[jira] [Commented] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/APLO-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092445#comment-13092445 ]
Hiram Chirino commented on APLO-20:
-----------------------------------
This optimization would also help topics that are configured with slow_consumer_policy="queue"
> 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
[jira] [Updated] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ 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.4)
1.5
> 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.5
>
>
> 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.
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
[jira] [Updated] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ 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.5)
1.6
> 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.6
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (APLO-20) Optimize session acked durable subs by
using a shared durable queue.
Posted by "Hiram Chirino (JIRA)" <ji...@apache.org>.
[ 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: 1.1
> 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