You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "clebert suconic (JIRA)" <ji...@apache.org> on 2019/03/14 18:28:04 UTC

[jira] [Closed] (ARTEMIS-2239) Zero-copy NIO/MAPPED TimedBuffer

     [ https://issues.apache.org/jira/browse/ARTEMIS-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

clebert suconic closed ARTEMIS-2239.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.0

> Zero-copy NIO/MAPPED TimedBuffer
> --------------------------------
>
>                 Key: ARTEMIS-2239
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-2239
>             Project: ActiveMQ Artemis
>          Issue Type: Improvement
>          Components: Broker
>    Affects Versions: 2.6.4
>            Reporter: Francesco Nigro
>            Assignee: Francesco Nigro
>            Priority: Major
>             Fix For: 2.7.0
>
>          Time Spent: 5h 50m
>  Remaining Estimate: 0h
>
> NIO/MAPPED journal types are currently performing the copy of the buffer used on TimedBuffer to accumulate writes, but this copy (and the zeroing of the new buffer) could be avoided, reducing dramatically the CPU usage and latencies during a burst of writes.
> An added benefit of this change is that isn't necessary anymore to stress the thread pool of the file factory, because there is no need to pool the buffer used to perform the write.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)