connection starvation problem
nginx-forum at nginx.us
Sun May 25 16:15:51 UTC 2014
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
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
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
starve other connections? SO do i miss something important? nginx how to
deal with this situation in read and write?
Posted at Nginx Forum: http://forum.nginx.org/read.php?2,250344,250344#msg-250344
More information about the nginx