activemq-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Justin Bertram (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ARTEMIS-717) Use hash buckets for JMSXGroupID to reduce system impact when there are lots of groups
Date Thu, 08 Sep 2016 14:20:20 GMT

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

Justin Bertram commented on ARTEMIS-717:
----------------------------------------

Can you quantify the "high burden" that the broker is under with a large number of groups?
 I'm mainly thinking of hot spots in the code where a lot of time is spent (e.g. stuff you
might find by attaching a profiler), but an application-level quantification would be fine
as well.

> 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
>            Reporter: Michael Brown
>
> 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)

Mime
View raw message