connection starvation problem
Valentin V. Bartenev
vbart at nginx.com
Mon May 26 09:20:01 UTC 2014
On Monday 26 May 2014 09:36:52 xinghua_hi wrote:
> In man epoll , a section refer to "epoll edge trigger starvation problem",
> and around to this we need to maintain a ready list instead of read socket
> until EAGAIN. but i didn't find any related solution code in nginx. In
> request body read function `ngx_http_do_read_client_request_body`, it seems
> that nginx will read socket buffer until EAGAIN or has read Content-length
> data. so if a client is fast enough and post data is large enough, is it
> possible to starve other connections? SO do i miss something important?
> nginx how to deal with this situation in read and write?
The question is: have you actually seen this problem in real life with a
typical TCP connection over network?
wbr, Valentin V. Bartenev
More information about the nginx-devel