Bug? Barage of hits leads to failure creating worker threads / stats tracking

[Artur Bergman]

I've never seen it do worker threads not created.

Are there any limits on number of threads? Can you get rid of - 
w1440,3000,60  and rely on the -p settings instead?

Artur

On Apr 11, 2009, at 12:46 PM, Ray Barnes wrote:

> Thanks for the reply, answers inline:
>
> On Fri, Apr 10, 2009 at 7:30 PM, John Adams <jna at twitter.com> wrote:
> Something's very wrong here - we've never experienced this before.
>
> Are you stating the server as root or as another user?
>
> As root.
>
> Any ulimit or restrictions on # of file descriptors?
>
> I'm manually setting ulimit in the script that starts varnishd, like  
> so:
>
> ulimit -n 131072
> ulimit -l 82000
> Other than that, and having manually set /proc/sys/fs/file-max to  
> 65535, all other settings are default according to RHEL 5 and Linux  
> 2.6.18 with Xen patches and backports maintained by xen.org (the  
> aforementioned results were all obtained by running varnish under  
> domain 0).  I tried this on another box which is RHEL 4.6 with  
> 2.6.9-55.0.2.ELsmp (so no Xen in this case), and /proc/sys/fs/file- 
> max set to 49984 (using the same script to launch varnish as  
> aforementioned), the result was relatively the same:
>
>          290  N worker threads
>          290  N worker threads created
>         8705  N worker threads not created
>       409188  N worker threads limited
> HTH.
>
> -Ray
>
> _______________________________________________
> varnish-dev mailing list
> varnish-dev at projects.linpro.no
> http://projects.linpro.no/mailman/listinfo/varnish-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-dev/attachments/20090411/0d428741/attachment-0001.html>