Github user revans2 commented on a diff in the pull request:
https://github.com/apache/incubator-storm/pull/103#discussion_r12810544
--- Diff: conf/defaults.yaml ---
@@ -109,6 +112,15 @@ storm.messaging.netty.max_retries: 30
storm.messaging.netty.max_wait_ms: 1000
storm.messaging.netty.min_wait_ms: 100
+# If the Netty messaging layer is busy(netty internal buffer not
writable), the Netty client will try to batch message as more as possible up to
the size of storm.messaging.netty.transfer.batch.size bytes, otherwise it will
try to flush message as soon as possible to reduce latency.
+storm.messaging.netty.transfer.batch.size: 262144
+
+# If storm.messaging.netty.blocking is set to true, the Netty Client will
send messages in synchronized way, otherwise it will do it in async way. Set
storm.messaging.netty.blocking to false to improve the latency and throughput.
--- End diff --
If this always improves the latency and throughput why have this as a
config option at all?
---
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.
---
