Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 29 Jun 2016 14:31:17 +0000 (UTC)
From: "Ted Yu (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12625731.1357163333000.258.1467210677556@Atlassian.JIRA>
In-Reply-To: <JIRA.12625731.1357163333000@Atlassian.JIRA>
References: <JIRA.12625731.1357163333000@Atlassian.JIRA> <JIRA.12625731.1357163333391@arcas>
Subject: [jira] [Commented] (HBASE-7478) Create a multi-threaded responder
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 29 Jun 2016 14:31:19 -0000


    [ https://issues.apache.org/jira/browse/HBASE-7478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15355326#comment-15355326 ] 

Ted Yu commented on HBASE-7478:
-------------------------------

I experimented with multi-threaded responder.
It was a bit slower for random read while a bit faster for range scan compared to single threaded Responder.


> Create a multi-threaded responder
> ---------------------------------
>
>                 Key: HBASE-7478
>                 URL: https://issues.apache.org/jira/browse/HBASE-7478
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: Karthik Ranganathan
>
> Currently, we have multi-threaded readers and handlers, but a single threaded responder which is a bottleneck.
> ipc.server.reader.count  : number of reader threads to read data off the wire
> ipc.server.handler.count : number of handler threads that process the request
> We need to have the ability to specify a "ipc.server.responder.count" to be able to specify the number of responder threads.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)