[
https://issues.apache.org/jira/browse/HBASE-16783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15567633#comment-15567633
]
ramkrishna.s.vasudevan commented on HBASE-16783:
------------------------------------------------
Yes. I have done some work to do the point 2 already. Patch will come later.
I think the default size is 64K and not 64M? Correct me if am wrong. Definitly
if it was 64M I would not have done this change.
bq.All using the pool is not making sense IMO
May be yes. That may be we can handle if we go with the 2nd way?
> Use ByteBufferPool for the header and message during Rpc response
> -----------------------------------------------------------------
>
> Key: HBASE-16783
> URL: https://issues.apache.org/jira/browse/HBASE-16783
> Project: HBase
> Issue Type: Improvement
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Attachments: HBASE-16783.patch, HBASE-16783_1.patch
>
>
> With ByteBufferPool in place we could avoid the byte[] creation in
> RpcServer#createHeaderAndMessageBytes and try using the Buffer from the pool
> rather than creating byte[] every time.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
