Valentin V. Bartenev
July 09, 2018 08:18AM
On Saturday 07 July 2018 08:15:43 stephan13360 wrote:
> Wow, thats it! The delay is gone.
>
> For now I am satisfied that the delay is gone and will read up some more on
> tcp_nopush.
>
> For the future: Is there any information on why the combination of
> tcp_nopush and proxy_cache_background_update create the delay and not the
> STALE response you get when the backend ist down and
> proxy_cache_background_update is off?
>

When a client connection is closing or switching to keepalive state,
the response body left in the socket is explicitly pushed. In current
implementation the client connection is kept "busy" during background
update and the last chunk may rest in the socket until kernel will send
it.

wbr, Valentin V. Bartenev

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

proxy_cache_background_update leads to 200 ms delay

stephan13360 July 06, 2018 08:32AM

Re: proxy_cache_background_update leads to 200 ms delay

stephan13360 July 06, 2018 09:55AM

Re: proxy_cache_background_update leads to 200 ms delay

Valentin V. Bartenev July 07, 2018 07:14AM

Re: proxy_cache_background_update leads to 200 ms delay

stephan13360 July 07, 2018 08:15AM

Re: proxy_cache_background_update leads to 200 ms delay

Lucas Rolff July 07, 2018 10:44AM

Re: proxy_cache_background_update leads to 200 ms delay

Valentin V. Bartenev July 09, 2018 08:18AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 189
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready