[
https://issues.apache.org/jira/browse/HBASE-14479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14965933#comment-14965933
]
stack commented on HBASE-14479:
-------------------------------
bq. In this jira issue, the benefit is not from this main advantage because we
just add the requests to queues.
Yeah, in a new issue, should we pull out the queue... Or, rather, I suppose in
a follow-on I could experiment with removing queues to see if it buys us
throughput. If it does, then we could look into redoing scheduling so it was
like the 'Bound handle/thread association' from the paper.
Thanks for looking at the WAL [~ikeda] I have a sense that this pattern might
help with the multiple-syncing threads... but let me try.
> Apply the Leader/Followers pattern to RpcServer's Reader
> --------------------------------------------------------
>
> Key: HBASE-14479
> URL: https://issues.apache.org/jira/browse/HBASE-14479
> Project: HBase
> Issue Type: Improvement
> Components: IPC/RPC, Performance
> Reporter: Hiroshi Ikeda
> Assignee: Hiroshi Ikeda
> Priority: Minor
> Attachments: HBASE-14479-V2 (1).patch, HBASE-14479-V2.patch,
> HBASE-14479-V2.patch, HBASE-14479.patch, gc.png, gets.png, io.png, median.png
>
>
> {{RpcServer}} uses multiple selectors to read data for load distribution, but
> the distribution is just done by round-robin. It is uncertain, especially for
> long run, whether load is equally divided and resources are used without
> being wasted.
> Moreover, multiple selectors may cause excessive context switches which give
> priority to low latency (while we just add the requests to queues), and it is
> possible to reduce throughput of the whole server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
