[ https://issues.apache.org/jira/browse/ARTEMIS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16383695#comment-16383695 ]
ASF GitHub Bot commented on ARTEMIS-1722: ----------------------------------------- Github user clebertsuconic commented on the issue: https://github.com/apache/activemq-artemis/pull/1918 SoftReference sucks. It usually let you OME before it’s released. What about having a pool somewhere else? Or a smaller pool from Netty? I’m out today and Monday. Can we talk about this when I get back on Tuesday? > 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)