Github user revans2 commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-43791269
Yes getting the best performance of a topology really depends on the
resources that your topology is using. If your topology is CPU bound then you
want to spread it out so that you have enough cores to handle the parallelism,
but if your topology is I/O bound you want to collocate them as much as
possible. The best performance optimization is simply to stop doing something.
So if you can cut out the serialization/deserialization and sending tuples to
another process, even over the loopback device, then that potentially becomes a
big win.
The really difficult part is that parts of your topology may be CPU bound,
other parts may be I/O bound, and other parts may be constrained by memory
(which has it's own limitations). Also you may have a different definition of
"best". Some users may require a very low latency, and are willing to let most
of the cluster sit idle so that they know when something happens they can
process it very quickly. Other times you are willing to sacrifice latency to
be sure that everything you want to run fits on a smaller set of hardware.
---
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.
---
