Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6020C200BB4 for ; Tue, 18 Oct 2016 07:39:00 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 5EBE1160AF2; Tue, 18 Oct 2016 05:39:00 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id CCBAA160AEC for ; Tue, 18 Oct 2016 07:38:59 +0200 (CEST) Received: (qmail 38219 invoked by uid 500); 18 Oct 2016 05:38:59 -0000 Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list issues@hbase.apache.org Received: (qmail 38159 invoked by uid 99); 18 Oct 2016 05:38:58 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2016 05:38:58 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id A8DF22C4C74 for ; Tue, 18 Oct 2016 05:38:58 +0000 (UTC) Date: Tue, 18 Oct 2016 05:38:58 +0000 (UTC) From: "ramkrishna.s.vasudevan (JIRA)" To: issues@hbase.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (HBASE-16783) Use ByteBufferPool for the header and message during Rpc response MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 18 Oct 2016 05:39:00 -0000 [ https://issues.apache.org/jira/browse/HBASE-16783?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15584529#comment-15584529 ] ramkrishna.s.vasudevan commented on HBASE-16783: ------------------------------------------------ My only concern was is it ok to add a new API in BBLOS though it is ugly? Since BBLOS handles curBuf it is difficult to bring out the buffer management outside without making other APIs also in that new class. Else for now can go with BBLOS itself but i fear we may have to do some refactoring later. thanks for the input. Will udpate the patch. > 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, HBASE-16783_2.patch, HBASE-16783_3.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)