[ https://issues.apache.org/jira/browse/ARTEMIS-1722?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16384093#comment-16384093 ]
ASF GitHub Bot commented on ARTEMIS-1722: ----------------------------------------- GitHub user tabish121 opened a pull request: https://github.com/apache/activemq-artemis/pull/1928 ARTEMIS-1722 Don't copy message bytes unless needed Alternate patch that doesn't copy the message bytes unless doing a redelivery or skipping delivery annotations in the original version of the message. Proton-J will copy the bytes provided to the Sender's send method so a copy isn't necessary on most common sends. You can merge this pull request into a Git repository by running: $ git pull https://github.com/tabish121/activemq-artemis ARTEMIS-1722 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/activemq-artemis/pull/1928.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #1928 ---- commit 63b2e84fce76a9bf6c7cc3c9cef00b775457453c Author: Timothy Bish <tabish121@...> Date: 2018-03-02T20:03:08Z ARTEMIS-1722 Don't copy message bytes unless needed Alternate patch that doesn't copy the message bytes unless doing a redelivery or skipping delivery annotations in the original version of the message. Proton-J will copy the bytes provided to the Sender's send method so a copy isn't necessary on most common sends. ---- > 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)