suggesting to increase timeout_req default to 7 seconds

[Geoff Simmons]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 03/25/2015 11:07 AM, Poul-Henning Kamp wrote:
> 
> Right now we have two timeouts:
> 
> timeout_idle - close idle connections after this long. [5 sec]
> 
> timeout_req - max time to collect req.hdrs (first->last byte) [2
> sec].
> 
> 
> Maybe we should instead have two different timeouts:
> 
> timeout_first - Time to receive first complete req.hdrs after
> accept.
> 
> timeout_idle - Time to receive subsequent complete req.hdrs after
> response.
> 
> Or maybe even just one:
> 
> timeout_idle - Time to receive complete req.hdrs

In my experience, the most common timeouts on the client side are the
idle timeout or timeout reading the request body (not the headers).
The latter shows up as a FetchError (at least in Varnish 3), since the
request body is read from the client and sent to a backend during fetch.

In other words, I don't see timeouts of the variety "time to first
req.hdr byte" or "time between req.hdr bytes" in real-world use. When
we're waiting, it's either to get a request at all, or to get the body.


Best,
Geoff
- -- 
** * * UPLEX - Nils Goroll Systemoptimierung

Scheffelstraße 32
22301 Hamburg

Tel +49 40 2880 5731
Mob +49 176 636 90917
Fax +49 40 42949753

http://uplex.de
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJVEox+AAoJEOUwvh9pJNURxSYP/2YptDhaFbqoL6TcXD4I/phn
tsOuS58rrzqKNFlgQCsNSGG+WZ64YOUbtio6DOv0Z8dpDajiueh7x8O3Vamjsn14
jlhoe3tewXH30iuSqBewBxyClbFgZtb57vWrm9BDWn3aDUjSxnv1+Ar0ZqvlcE5W
IR2zF2PKymiktgX0d2qNTWK8jGx6Enb4Q2ORRHFZrZntXxIIL/N5TXm9YT5nGpbR
jDYaAf0pcAYBz5OKtZ+1SiDOfNuuDa9HuZmb9OB5BMSKRmekhnwPQY/KvnDtLe2F
N5joDL2E+IhuI9huXHFdexNZQk+QZU3vjR/W2h1KRokua2afZIkzJc55JrZqtGhy
qwcY46Ad/uX1CjfbTDr0Q8LIJ0hBR4ciaFmlnLoPZ63gofFHQF8TYzMrK2xRbUDC
3vU5+w43DM0ufDNZ6/XZ7IhxvCOzwZXkfoAezn9KCqXNJMS+rbcYIP+CNxmb/c0i
wumPPFlAsl6mZ0lqbpMdcFGV43nMApW1iVdHDItM5vrb2FccE7orqg2B4VVCrpgt
fX088Vp8F8jgvRa0pC+XfSZyAM3gEj2WrGb2+Q10LdG9BLN+1zLz66KIw+mbEFS/
nwQEaJSPHIkAmdJcqZXYP8LmdnnYavMY+LollQtvcKMzsyeULXL7Ahmn8IQswMgj
9+DH5OCi3zT7sTvq2tGG
=1G/t
-----END PGP SIGNATURE-----