[
https://issues.apache.org/jira/browse/HBASE-15756?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15400713#comment-15400713
]
stack commented on HBASE-15756:
-------------------------------
Yes. It is the same as we have except in regard to response being possible
multithreaded.
Our Listener thread == Boss Worker
Our Reader threads == Worker
Our single Responder == Worker (but we only have one Responder but profiling,
the Handler thread usually writes direct on the socket)
I didn't expect any speedup but perhaps netty does Select handling better and
responding, we may clash more often and netty does a better job doing the
reply. I could test more extensively. Any chance of a patch with netty4? We
don't want to commit a netty3-based patch.
> Pluggable RpcServer
> -------------------
>
> Key: HBASE-15756
> URL: https://issues.apache.org/jira/browse/HBASE-15756
> Project: HBase
> Issue Type: Improvement
> Components: Performance, rpc
> Reporter: binlijin
> Assignee: binlijin
> Priority: Critical
> Attachments: NettyRpcServer.patch, NettyRpcServer_forperf.patch,
> gets.png, idle.png, queue.png
>
>
> Current we use a simple RpcServer, and can not configure and use other
> implementation.This issue is to make the RpcServer pluggable, so we can make
> other implementation for example netty rpc server. Patch will upload laterly
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
