Trying to Understand Upstream Keepalive

[newnovice]

Maxim Dounin Wrote:
-------------------------------------------------------
> Hello!
> 
> On Tue, Oct 28, 2014 at 08:01:33PM -0400, newnovice wrote:
> 
> > Maxim, 
> > 
> >
> http://nginx.org/en/docs/http/ngx_http_upstream_module.html#keepalive
> > 
> > I would like to know what is the keepalive timeout for this
> connection pool?
> > Is it static? 
> 
> As of now, there is no timeout on nginx side.  Connections are 
> closed either by backends or if there isn't enough room in 
> the cache.

So how long after a connection to upstream goes from ACTIVE to idle in the
connection pool does it get closed? 
There is not really much documentation on this upstream keepalive component.


> 
> > Also i want to understand - if there is a marriage between number of
> > connections nginx gets vs how many it opens to upstream? 
> 
> This depends on how long it takes to process a request (as well as 
> various other factors).  As long as backends are fast enough, one 
> connection to upstream may be enough to handle tens or hundreds of 
> client connections.

Ok. 
What is the difference between 'max_conns' vs
http://nginx.org/en/docs/http/ngx_http_limit_conn_module.html#limit_conn to
an upstream service ? 

> 
> -- 
> Maxim Dounin
> http://nginx.org/
> 
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx

Posted at Nginx Forum: http://forum.nginx.org/read.php?2,249924,254418#msg-254418