Github user Gvain commented on the pull request:
https://github.com/apache/incubator-storm/pull/103#issuecomment-45091025
@clockfly
Thanks for your explanation. The explanation for part 2 seems not so
convincing as the CPU and network are not saturated at both env when scaling
worker# from 4 to 8. Oops, I don't wanna go any further on this.
Anyway, your work is really great.
Another thing. Since you use netty to send message in a async way, how can
you ensure that all messages emitted from a fast component are received by a
slow component without any loss especially under heavy throughput without any
ackers enabled ? To my knowledge, the netty channel may not be writable, and
pendings count will increase.
---
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.
---
