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 th
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
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 i
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
Hello!
On Sat, Mar 03, 2018 at 10:27:21PM -0500, Sergey Sandler wrote:
> I am running Nginx as a proxy for a single-threaded server (Shiny R) in
> Windows;both the proxy and the server are located on the same machine. There
> are delays due to timeout errors:
> "upstream timed out: A connecti
Hi,
I am running Nginx as a proxy for a single-threaded server (Shiny R) in
Windows;both the proxy and the server are located on the same machine. There
are delays due to timeout errors:
"upstream timed out: A connection attempt failed because the connected
party did not properly respond after
