Github user HeartSaVioR commented on the issue:
https://github.com/apache/storm/pull/2241
From now what I can suggest is... breaking down STORM-2306 to "redesign
messaging subsystem" and "switch to JCTools Queues", and try out latter part
first.
Let's just have new pull request only replacing Disruptor with JCQueue and
see it helps. I'd rather lean on putting the minimal effort and make it better
incrementally. This patch mixes up everything (micro optimization, switching
queue, messaging architecture change) in one, so hard to point out where the
issue starts.
And let's separate micro-optimization (converting map usage to array list,
avoiding iterator, etc.) as another issue and don't address them from other
issues. I think we should have better throughput even without them if newer
subsystem is better and/or JCTools Queues are better than Disruptor in our case.
---
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.
---
