You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "Francesco Nigro (Jira)" <ji...@apache.org> on 2021/08/30 12:57:00 UTC
[jira] [Updated] (ARTEMIS-3449) Speedup AMQP large message
streaming
[ https://issues.apache.org/jira/browse/ARTEMIS-3449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Nigro updated ARTEMIS-3449:
-------------------------------------
Description: AMQP is using unpooled heap ByteBuffer(s) to stream AMQP large messages: given that the underline NIO sequential file can both use FileChannel or RandomAccessFile (depending if the ByteBuffer used is direct/heap based), both approaches would benefit from using direct ByteBuffers pooled from Netty and save additional copies (performed by RandomAccessFile) to happen, reducing GC too. (was: AMQP is using heap ByteBuffer(s) to stream AMQP large messages: given that the underline NIO sequential file can both use FileChannel or RandomAccessFile (depending if the ByteBuffer used is direct/heap based), both approaches would benefit from using direct ByteBuffers pooled from Netty and save additional copies (performed by RandomAccessFile) to happen, reducing GC too.)
> Speedup AMQP large message streaming
> ------------------------------------
>
> Key: ARTEMIS-3449
> URL: https://issues.apache.org/jira/browse/ARTEMIS-3449
> Project: ActiveMQ Artemis
> Issue Type: Improvement
> Reporter: Francesco Nigro
> Assignee: Francesco Nigro
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> AMQP is using unpooled heap ByteBuffer(s) to stream AMQP large messages: given that the underline NIO sequential file can both use FileChannel or RandomAccessFile (depending if the ByteBuffer used is direct/heap based), both approaches would benefit from using direct ByteBuffers pooled from Netty and save additional copies (performed by RandomAccessFile) to happen, reducing GC too.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)