Read starvation

[ArvidSvensson]

Hi!

I'm writing lots of messages from at Netty NIO server to a couple of
thousand clients. 
Whenever I get an ChannelFutureListener#operationComplete from a write's
ChannelFuture I write new messages at hand (if the channel is writable). 
I also write new messages at hand when getting
SimpleChannelHandler#channelInterestChanged indicating that the channel is
writable. 

The problem is that I starve read operations when doing this. The clients
are sending heartbeats that the server doesn't let in in time.
All the I/O workers are busy writing messages. How can I make netty fair on
the reads?

If I don't utilize the operationComplete/channelInterestChanged callbacks I
can't get any speed out netty (see my initial problem at
http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Slow-writes-from-outside-an-I-O-worker-td6817213.html#a6820504
).


Regards,
Arvid



--
View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Read-starvation-tp6876802p6876802.html
Sent from the Netty User Group mailing list archive at Nabble.com.