[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-717: Fix Version/s: (was: 2.3.0) 2.4.0 > Use hash buckets for JMSXGroupID to reduce system impact when there are lots > of groups > -- > > Key: ARTEMIS-717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-717 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.4.0 >Reporter: Michael Brown > Fix For: 2.4.0 > > > Currently Artemis maintains an association of JMSXGroupID to consumer on a > one to one level, puting high burden on the broker. > The sibiling project ArtemisMQ has solved this with the use of hash buckets. > I suggest that Artemis does the same. > https://issues.apache.org/jira/browse/AMQ-439 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-717: Fix Version/s: (was: 2.2.0) 2.3.0 > Use hash buckets for JMSXGroupID to reduce system impact when there are lots > of groups > -- > > Key: ARTEMIS-717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-717 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.4.0 >Reporter: Michael Brown > Fix For: 2.3.0 > > > Currently Artemis maintains an association of JMSXGroupID to consumer on a > one to one level, puting high burden on the broker. > The sibiling project ArtemisMQ has solved this with the use of hash buckets. > I suggest that Artemis does the same. > https://issues.apache.org/jira/browse/AMQ-439 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-717: Fix Version/s: (was: 2.1.0) 2.2.0 > Use hash buckets for JMSXGroupID to reduce system impact when there are lots > of groups > -- > > Key: ARTEMIS-717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-717 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.4.0 >Reporter: Michael Brown > Fix For: 2.2.0 > > > Currently Artemis maintains an association of JMSXGroupID to consumer on a > one to one level, puting high burden on the broker. > The sibiling project ArtemisMQ has solved this with the use of hash buckets. > I suggest that Artemis does the same. > https://issues.apache.org/jira/browse/AMQ-439 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martyn Taylor updated ARTEMIS-717: -- Fix Version/s: (was: 2.0.0) 2.next > Use hash buckets for JMSXGroupID to reduce system impact when there are lots > of groups > -- > > Key: ARTEMIS-717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-717 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.4.0 >Reporter: Michael Brown > Fix For: 2.next > > > Currently Artemis maintains an association of JMSXGroupID to consumer on a > one to one level, puting high burden on the broker. > The sibiling project ArtemisMQ has solved this with the use of hash buckets. > I suggest that Artemis does the same. > https://issues.apache.org/jira/browse/AMQ-439 -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-717: Fix Version/s: (was: 1.5.1) 1.6.0 > Use hash buckets for JMSXGroupID to reduce system impact when there are lots > of groups > -- > > Key: ARTEMIS-717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-717 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.4.0 >Reporter: Michael Brown > Fix For: 1.6.0 > > > Currently Artemis maintains an association of JMSXGroupID to consumer on a > one to one level, puting high burden on the broker. > The sibiling project ArtemisMQ has solved this with the use of hash buckets. > I suggest that Artemis does the same. > https://issues.apache.org/jira/browse/AMQ-439 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-717: Fix Version/s: (was: 1.5.0) 1.6.0 > Use hash buckets for JMSXGroupID to reduce system impact when there are lots > of groups > -- > > Key: ARTEMIS-717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-717 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.4.0 >Reporter: Michael Brown > Fix For: 1.6.0 > > > Currently Artemis maintains an association of JMSXGroupID to consumer on a > one to one level, puting high burden on the broker. > The sibiling project ArtemisMQ has solved this with the use of hash buckets. > I suggest that Artemis does the same. > https://issues.apache.org/jira/browse/AMQ-439 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
[ https://issues.apache.org/jira/browse/ARTEMIS-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] clebert suconic updated ARTEMIS-717: Affects Version/s: 1.4.0 Fix Version/s: 1.5.0 > Use hash buckets for JMSXGroupID to reduce system impact when there are lots > of groups > -- > > Key: ARTEMIS-717 > URL: https://issues.apache.org/jira/browse/ARTEMIS-717 > Project: ActiveMQ Artemis > Issue Type: New Feature > Components: Broker >Affects Versions: 1.4.0 >Reporter: Michael Brown > Fix For: 1.5.0 > > > Currently Artemis maintains an association of JMSXGroupID to consumer on a > one to one level, puting high burden on the broker. > The sibiling project ArtemisMQ has solved this with the use of hash buckets. > I suggest that Artemis does the same. > https://issues.apache.org/jira/browse/AMQ-439 -- This message was sent by Atlassian JIRA (v6.3.4#6332)