title: Is there any point in using Netty with Disruptor performance-wise?
body: <p>I am building a simple reactive server which should consume incoming protobuf/protostuff messages from multiple clients, execute some business logic on them and possibly send fire-and-forget messages to other consumers.
  I want to implement transport and decoding part in Netty. My question is: is there any point on publishing decoded messages to the Disruptor's ring buffer performance-wise or the extra performance offered by Disruptor would be negated by internal Netty scheduling? Should I provide Netty with two threads (one for "accept" and other for "connect" group) or just one is better? Maybe, I should just split messages by length field in Netty's handlers, and execute decoding in Disruptor's ones?</p>