[
https://issues.apache.org/jira/browse/STORM-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13959009#comment-13959009
]
Nathan Marz commented on STORM-272:
-----------------------------------
It would be a good experiment, but we'd have to make sure that incoming
messages from the same task always go to the same receiver thread (otherwise
messages sent by a task to another task could be received out of order)
> Make worker receiver thread number configurable
> -----------------------------------------------
>
> Key: STORM-272
> URL: https://issues.apache.org/jira/browse/STORM-272
> Project: Apache Storm (Incubating)
> Issue Type: Improvement
> Affects Versions: 0.9.2-incubating
> Reporter: Sean Zhong
> Priority: Minor
>
> In my profiling, I found the receiver thread of worker can be a performance
> bottle-neck.
> Now each worker has single receiver thread, and it is responsbile to transfer
> information generated from multiple netty client to tens of executor
> disruptor queue. It is too much for busy topology.
> Without this fix, we have to increase the number of workers, which will
> create more intra-worker traffic that we don't want.
>
> I suggest that we can add a config called "worker.receiver.thread.count" to
> control the parallism of the receiver thread, and make it default to 1.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
