[
https://issues.apache.org/jira/browse/ARTEMIS-2239?focusedWorklogId=197513&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-197513
]
ASF GitHub Bot logged work on ARTEMIS-2239:
-------------------------------------------
Author: ASF GitHub Bot
Created on: 12/Feb/19 12:00
Start Date: 12/Feb/19 12:00
Worklog Time Spent: 10m
Work Description: michaelandrepearce commented on issue #2522:
ARTEMIS-2239 Zero-copy NIO/MAPPED TimedBuffer
URL: https://github.com/apache/activemq-artemis/pull/2522#issuecomment-462732912
Looking promising. @franz1981 with all the changes youve been working on for
journals, im not sure what the merge order is. Can this just be merged OR do we
need merge another PR first?
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 197513)
Time Spent: 5.5h (was: 5h 20m)
> 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
> Time Spent: 5.5h
> 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)
