On Tue, Mar 06, 2018 at 10:38:21PM -0500, Sergey Sandler wrote:
> Thank you, Valentin.
>
> There is something I am missing. Please see the start of the error.log
> below,
>
> 2018/03/04 14:05:50 [notice] 5144#9212: using the "select" event method
> 2018/03/04 14:05:50 [notice] 5144#9212: using
Thank you, Valentin.
There is something I am missing. Please see the start of the error.log
below,
2018/03/04 14:05:50 [notice] 5144#9212: using the "select" event method
2018/03/04 14:05:50 [notice] 5144#9212: using the "select" event method
2018/03/04 14:05:50 [notice] 5144#9212: nginx/1.12.2
On Monday 05 March 2018 19:46:42 Sergey Sandler wrote:
> Hi Maxim,
>
> Thank you for prompt reply.
>
> I suspect there would be no delays/timeouts if there was a single thread in
> nginx that communicates with the upstream server.
> There is no simple way to restrict nginx threads number to one
Hi Maxim,
Thank you for prompt reply.
I suspect there would be no delays/timeouts if there was a single thread in
nginx that communicates with the upstream server.
There is no simple way to restrict nginx threads number to one in Windows?
Serving static files directly by nginx will likely solve
ports: unknown directive "thread_pool".
The error message indicate that your upstream server can't cope
with load. Using thread pools in nginx won't help you with this,
you need to either tune your upstream server to handle more load,
or move some load away from it, e.g., by s
