[
https://issues.apache.org/jira/browse/DEFT-112?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070144#comment-13070144
]
Emmanuel Lecharny commented on DEFT-112:
----------------------------------------
As Julien mentionned, pooling BB would put a strain on the JVM, simply because
this pool will have to be synchronized to some extent. The JVM GC does a way
better work at providing newly allocated blocks of data taken from a pool.
Regarding the Direct/heap buffer, when we did some experiments 3 years ago,
HeapBuffer were way less expensive to create. We have had a discussion with
Seven this week, it seems that in Java 7, this is not the same story. It would
be interesting to conduct some tests with the new JVM.
> Optimized ByteBuffer usage in AsynchronousSocket
> ------------------------------------------------
>
> Key: DEFT-112
> URL: https://issues.apache.org/jira/browse/DEFT-112
> Project: Deft
> Issue Type: Improvement
>
> The ByteBuffer usage is HttpProtocol is pretty optimized (bytebuffer reusage
> etc). Apply the similiar usage in AS
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
