[
https://issues.apache.org/jira/browse/ARTEMIS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383707#comment-16383707
]
ASF GitHub Bot commented on ARTEMIS-1722:
-----------------------------------------
Github user tabish121 commented on the issue:
https://github.com/apache/activemq-artemis/pull/1918
@franz1981 It doesn't look like the buffer could be contended unless
perhaps the consumer was able to be subscribed to more than one queue at a time
via some sort of composite type subscription but I don't think that is possible
? otherwise the broker should be dispatching serially if I understand
correctly but I'd defer to @clebertsuconic on that one.
It isn't entirely uncommon for consumers to be subscribed to low volume
queues or topics where they might sit idle for a longer period of time so
having each consumer hold onto memory like that indefinitely could lead to
quick resource exhaustion on the broker in the case of 1000s of connections
(think IoT)
> Reduce pooled Netty ByteBuf usage
> ---------------------------------
>
> Key: ARTEMIS-1722
> URL: https://issues.apache.org/jira/browse/ARTEMIS-1722
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Components: AMQP, Broker
> Affects Versions: 2.4.0
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Fix For: 2.5.0
>
> Original Estimate: 3h
> Remaining Estimate: 3h
>
> Pooled Netty Heap ByteBuf could be avoided thanks to smart pooling on hot
> paths, improving scalability and memory footprint.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
