[
https://issues.apache.org/jira/browse/HBASE-10573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13907250#comment-13907250
]
Nick Dimiduk commented on HBASE-10573:
--------------------------------------
bq. What specifically would you suggest in the alternative?
I don't have anything else at this time, perhaps except for ByteBuffers + some
reflection voodoo. This has the benefit of sticking with the JVM "native" APIs,
but has the down side of reflection voodoo. I wrote up a little benchmark a
while back, comparing allocating new DirectByteBuffers vs. reusing a single
instance and re-assigning it with reflection. Reflection was slower than a
single allocation, but I it didn't account for the collection afterwords. I
also don't think the synthetic microbenchmark is indicative of use in the real
system. In any case, even if dbb + reflection proves viable, we don't get the
many other benefits you itemize above. DirectByteBuffers + reflection does open
up the possibility of using the unsafe directly to manage memory, which may be
desirable.
As you say, more investigation is necessary :)
> Use Netty 4
> -----------
>
> Key: HBASE-10573
> URL: https://issues.apache.org/jira/browse/HBASE-10573
> Project: HBase
> Issue Type: Sub-task
> Affects Versions: hbase-10191
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Attachments: 10573.patch
>
>
> Pull in Netty 4 and sort out the consequences.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
