[
https://issues.apache.org/jira/browse/HBASE-15202?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15133962#comment-15133962
]
Hudson commented on HBASE-15202:
--------------------------------
SUCCESS: Integrated in HBase-1.3 #537 (See
[https://builds.apache.org/job/HBase-1.3/537/])
HBASE-15202 Reduce garbage while setting response (Ram) (ramkrishna: rev
38e79b09c9a7eed7e76ae7b8eecbf10794cd0765)
* hbase-server/src/main/java/org/apache/hadoop/hbase/ipc/RpcServer.java
> Reduce garbage while setting response
> -------------------------------------
>
> Key: HBASE-15202
> URL: https://issues.apache.org/jira/browse/HBASE-15202
> Project: HBase
> Issue Type: Sub-task
> Components: regionserver
> Reporter: ramkrishna.s.vasudevan
> Assignee: ramkrishna.s.vasudevan
> Priority: Minor
> Fix For: 2.0.0, 1.3.0
>
> Attachments: HBASE-15202.patch, HBASE-15202_1.patch,
> HBASE-15202_2.patch, HBASE-15202_3.patch
>
>
> Probably this can move under HBASE-15177. During RpcServer#setResponse we do
> IPCUtil.getDelimitedMessageAsByteBuffer for the header and result. This
> internally creates a byte[], CodedOutputStream and a BB. Then the totalSize
> is also wrapped in a BB.
> Finally all these BB are passed to BufferChain along with the Cellblock.
> This JIRA is to reduce the number of objects that we create here and allow
> one BB from this header, result and total Size along with one
> CodedOutputStream and pass this BB along with the Cellblocks to the
> Bufferchain. From the JMC tool can observe around 2% lesser object allocation
> arising out of these objects.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
