[
https://issues.apache.org/jira/browse/HBASE-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13877326#comment-13877326
]
stack commented on HBASE-10374:
-------------------------------
[~jianbginglover] You suggest jemalloc for memstore block allocations. What
are you thinking we'll see by way of benefit? I'd think that isolating the
MemStore and then in a simple testing harness trying various options would be
the way to go (MemStore can be stood up outside of a HStore IIRC). Try netty
implementation first since code is done. See if you can get any speedup in
your testing rig. If improvement, then lets talk. We'll have to see about
what [~ndimiduk] reminds us of, that netty implemenation is ByteBuf-based (as
opposed to ByteBuffer).
On pulling in netty4, it might not be too bad since they changed the package
from org.jboss to io.netty.
> add jemalloc into the choice of memstore allocation
> ----------------------------------------------------
>
> Key: HBASE-10374
> URL: https://issues.apache.org/jira/browse/HBASE-10374
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.96.1.1
> Reporter: Bing Jiang
> Priority: Minor
>
> https://blog.twitter.com/2013/netty-4-at-twitter-reduced-gc-overhead
> introduced that Netty used jemalloc to gain benefits from GC.
> It can be a good choice for memstore block allocation.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
