Something to take into account: if you limit the bandwidth,
a nginx worker will have to spend more time for that request,
time he cannot spend on other, possibly more meaningful
requests.
> On 24 Dec 2021, at 14:23, Francis Daly wrote:
>
> On Thu, Dec 23, 2021 at 09:53:26AM +0800, huiming wrote:
6/how-guides/what-timewait-state
cf.
https://onlinehelp.opswat.com/centralmgmt/What_you_need_to_do_if_you_see_too_many_TIME_WAIT_sockets.html
On 20 Dec 2021, at 20:35, Maxim Dounin
mailto:mdou...@mdounin.ru>> wrote:
Hello!
On Mon, Dec 20, 2021 at 04:00:59PM +, Nicolas Franck wrote:
In
fcgi workers are holding on to a connection to an nginx worker,
and there seems to be no queue handling this.
Is this correct? Just guessing here
> On 20 Dec 2021, at 15:11, Maxim Dounin wrote:
>
> Hello!
>
> On Sun, Dec 19, 2021 at 07:56:51PM +, Nicolas Franck wrote:
>
&
I've created a server setup where nginx acts as
a proxy server for a fastcgi application.
That last application is running on a different server on port 9000.
It is spawn with spawn-fcgi.
Recently I have found out that nginx
closes the connection after every request.
In order to make nginx keep th
