Miscellaneous questions

[Dag-Erling Smørgrav]

"Poul-Henning Kamp" <phk at phk.freebsd.dk> writes:
> "Michael S. Fischer" <michael at dynamine.net> writes:
> > "Dag-Erling Smørgrav" <des at linpro.no> writes:
> > > "Michael S. Fischer" <michael at dynamine.net> writes:
> > > > "Dag-Erling Smørgrav" <des at linpro.no> writes:
> > > > > I think the default timeout on backends connection may be a
> > > > > little short, though.
> > > > I assume this is the thread_pool_timeout parameter?
> > > No, that's how long an idle worker thread is kept alive.  I don't
> > > think the backend timeout is configurable, I think it's hardocded
> > > to five seconds.
> > What does the timeout pertain to?  Connect time?  Response time?
> Actually, I don't think we have any non-default timeout on the
> backends now: connect timeout is whatever the kernel uses and we don't
> set any socketopts like SO_RCVTIMEO on the tcp connection.

No, we were talking about how long an idle backend connection is kept
open (or at least I was).

Here's some additional context:

"Dag-Erling Smørgrav" <des at linpro.no> writes:
> "Poul-Henning Kamp" <phk at phk.freebsd.dk> writes:
> > "Michael S. Fischer" <michael at dynamine.net> writes:
> > > (2) HTTP/1.1 keep-alive connection reuse:  Does Varnish have the
> > > ability to reuse origin server connections (assuming they are HTTP/1.1
> > > Keep-Alive connections)?  Or, is there a strict 1:1 mapping between
> > > client-proxy connections and proxy-origin server connections?
> > They should already be reused by default.
>
> Maybe something is preventing backend session reuse in his
> installation; that can easily be determined from logs.
>
> I think the default timeout on backends connection may be a little
> short, though.

DES
-- 
Dag-Erling Smørgrav
Senior Software Developer
Linpro AS - www.linpro.no