many workers threads failed with EAGAIN

[David Birdsong]

ok, this time it's completely wedged.

it's resetting all new tcp connections to the process.  if i check
status through the mangament port, says the child is alive.

On Tue, Sep 1, 2009 at 2:19 AM, David Birdsong<david.birdsong at gmail.com> wrote:
> misses favor 1e-2[s]  with a few at 1e-1[s]
>
>
> after retesting on a 16Gb machine, i'm getting much better results.
> but still after varnish consumes all ram, iowait goes up, process load
> skyrockets to like 2200 processes marked for run.  sometimes varnish
> recovers in 5 minutes and others in about 1 minute.  this makes me
> think that all the threads are piling up for something like access to
> the lru list.
>
> when i first starting testing tonight, the first pile-up was at 1 hour
> which was what my lru_interval was set to.  i've since reduced via
> varnishadm to 10 mins and it now hangs as soon as ram is
> consumed(which takes a little over 10 mins).  i tried re-raising it to
> 3600 and even 4200, but it still seems to pile up sooner.
>
> here's what a few graphs look like...
> http://img162.imageshack.us/img162/9300/hourlyvarnishhang.png
>
> aside from these pile-ups, i'm almost to a workable state.  though i'd
> like to increase the backends to 5-6 if possible.
>
> On Tue, Sep 1, 2009 at 1:59 AM, Poul-Henning Kamp<phk at phk.freebsd.dk> wrote:
>> In message <dcccdf790908311636g39bbf036icdc66405e46aa919 at mail.gmail.com>, David
>>  Birdsong writes:
>>
>> What does your responstimes look like in varnishhist ?
>>
>> --
>> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
>> phk at FreeBSD.ORG         | TCP/IP since RFC 956
>> FreeBSD committer       | BSD since 4.3-tahoe
>> Never attribute to malice what can adequately be explained by incompetence.
>>
>