Starvation

[Nat]

Hi,

I noticed that if under a high load where Netty processes a lot of lengthy http requests (>MB). It could happen that the event loop thread is busy processing a single stream of http request and leave the other to delay much further behind (especially when you can process the request much slower than the incoming rate). It is quite similar to the starvation which was addressed by netty io ratio setting. However, this is the problem where requests starve each other. I wonder whether there is a good strategy to ensure that each request is given enough time slice to process some data.

Thanks,