Github user roshannaik commented on the issue:
https://github.com/apache/storm/pull/2241
For the new messaging system.. the scaling rule of thumb I have found so
far is quite simple.
For fast topos (and CPU intensive topos) ... 1 executor thread per
*physical core*. It applies to ACKer executors as well. Avoid trying to max
out on logical cores / hyperthreads.
You are likely to be close to getting the most out of your hardware with
that rule. You can start with that and try adding/removing one or more
executors to see if you can squeeze more.
The older system will typically need more executors per machine to get
similar numbers (throughput&cpu usage).. but throughput may not come close to
the new system.
The rule for executors count v/s CPU cores for the existing msgs system
seems less simple to me.
Trying to run 51 executors on a 4 core machine will surely be a step
towards "de-scaling", if there is such a word. It is strange that such high
executor count was useful in the current system.
---
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 infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
