Hello,

I'm very new to storm world and the list, so Hello from Turkey.

Because of a recent incident we had to increase our openstack network bandwidth soft limits from 1gb/s to 2gb/s.

And of course even though the problem resides in our tuples' size and topology size, I thought if storm's netty was using ZlibEncoding. Looking into backtype.storm.messaging.netty.StormServerPipelineFactory and client counterpart, pipline seems to not have any compression handlers.

Is it an intentional decision to not include compression in the pipeline? I know it would need more processing power and reduce topology performance, but I would like to know it it was considered before, and if not raise the issue.

Thank you.

Reply via email to