Github user clockfly commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-43656390
Gvain,
> Besides, By using a SHARED threadpool(its default size is 1) among all
netty client within a worker, the netty threads number do not increase as
total worker numbers increase. Check [jira][storm-12]. So, increasing worker
count may not cause netty context switching problem.
Context switch here means netty threads from different worker processes of
same machine will compete with each other.
> "3. More outbound acker message count. Usually we will allocate one acker
to one worker."
But you allocate 48 ackers to only 4 workers.
Usually one acker one worker will suffice. But for the perfomance
benchmarking case, acker becomes a bottleneck, because the message count is
huge.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
