Github user miguno commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-45060188
@clockfly Beyond the specific work on this item (STORM-297) what would be
your lessons learned after having investigated Storm's performance and
scalability so closely, i.e. with regards to potential bottlenecks (= things
that are broken and that need fixing) or areas where we still have untapped
potential (= where we could optimize further, maybe simply because we haven't
focused on a particular piece of the architecture/code/... yet)?
For instance, would you say that there are some general design-related
decisions that could put an upper bound on Storm's scalability (in theory
and/or in practice)? Or would you say it is, at least at this point in time,
more the current implementation of the design? Just thinking aloud.
I'd appreciate any comments -- positive or negative -- you might have in
this context.
---
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.
---
