hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj Das (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-6103) Optimize the HBaseServer to deserialize the data for each ipc connection in parallel
Date Wed, 16 Jan 2013 00:32:14 GMT

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

Devaraj Das commented on HBASE-6103:
------------------------------------

Ugh I meant to say HBASE-2941 (and not HBASE-2713).
                
> Optimize the HBaseServer to deserialize the data for each ipc connection in parallel
> ------------------------------------------------------------------------------------
>
>                 Key: HBASE-6103
>                 URL: https://issues.apache.org/jira/browse/HBASE-6103
>             Project: HBase
>          Issue Type: Improvement
>          Components: Performance
>            Reporter: Liyin Tang
>            Assignee: Liyin Tang
>         Attachments: HBASE-6103-fb-89.patch
>
>
> Currently HBaseServer is running with a single listener thread, which is responsible
for accepting the connection, reading the data from network channel, deserializing the data
into writable objects and handover to the IPC handler threads. 
> When there are multiple hbase clients connecting to the region server (HBaseServer) and
reading/writing a large set of data, the listener and the respond thread will be performance
bottleneck. 
> So the solution is to deserialize the data for each ipc connection in parallel for HBaseServer
> BTW, it is also one of the reasons that the parallel scanning from multiple clients is
far slower than single client case.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message