Welcome! Log In Create A New Profile


connection starvation problem

May 25, 2014 12:15PM

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?

Subject Author Posted

connection starvation problem

xinghua_hi May 25, 2014 12:15PM

Re: connection starvation problem

Maxim Dounin May 26, 2014 07:46AM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 195
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready