Connections dropped under load

[George Georgovassilis]

Hello Poul-Henning,

I need to correct you there:

1. The benchmark replicates an expected real-life sequence of requests 
and workload from a single IP (namely a corporate web-proxy), thus 
labelling it "synthetic" does it no justice :-)
2. If you leave "session_linger" out of the configuration (so not 
mentioning it at all) the benchmark still hangs. Whatever the default 
value is, it doesn't work and I explicitly need to reduce it to 20.


On 06.01.2011 00:36, Poul-Henning Kamp wrote:
> In message<4D24FD97.1070502 at gmail.com>, George Georgovassilis writes:
>> This is a multi-part message in MIME format.
>> In the meantime I found an unlikely setting that solved my problem: the
>> session_linger. I got it from here [1] and thought it wouldn't hurt and
>> it nearly killed me. My initial tests were conducted with a value of
>> 150, I had to lower it to 20 to get my test through.
> session_linger is marked EXPERIMENTAL for a reason:  I have no idea
> what a good default value is.
>
> It is one of those that has the potential to make synthetic benchmarks
> totally unrelated to real life traffic, so you should never tune it
> based on synthetic benchmarks.
>