Bret,
Thanks for the reply - that appears to put us (perhaps) a little closer.
I'm assuming for the moment when you said "init script" that you meant the
script I use to call up varnish and not the script that boots the box as per
/etc/inittab. When I specify "ulimit -s 1024" it did not change the net
result of varnish's inability to create threads:
192 N worker threads
424 N worker threads created
62 N worker threads not created
However the C program I posted previously in this discussion was able to
create 3055 threads. Hope that helps.
-Ray
On Tue, Apr 14, 2009 at 2:57 PM, Bret A. Barker <b...@iwin.com> wrote:
> Try a "ulimit -s 1024" in your init script. Definitely sounds like a
> problem with thread stack size defaulting to 8192.
>
> -bret
>
> On Tue, Apr 14, 2009 at 02:31:31PM -0400, Ray Barnes wrote:
> > Thanks for the reply. With those settings, same result:
> >
> > 192 N worker threads
> > 284 N worker threads created
> > 21 N worker threads not created
> > Again, the issue is apparently that the _operating system_ does not let
> me
> > create more than 300ish threads.
> >
> > -Ray
> >
> >
> >
> > On Tue, Apr 14, 2009 at 2:19 PM, Rafael Umann <rafael.um...@terra.com.br
> >wrote:
> >
> > >
> > > What about the cache size? have you decresead it?
> > >
> > > Try running varnish with:
> > >
> > > # varnishd -f /etc/varnish/default.vcl \
> > > -a 0.0.0.0:80 <http://0.0.0.0/> <http://0.0.0.0/> \
> > > -s file,/var/lib/varnish/varnish_storage.bin,50M \
> > > -T 0.0.0.0:6082 \
> > > -u varnish \
> > > -g varnish \
> > > -w 500,500,120 \
> > > -p lru_interval=900 \
> > > -p thread_pools=1 \
> > > -P /var/run/varnish/varnish.pid \
> > > -F"
> > >
> > > []s,
> > >
> > >
>
>
_______________________________________________
varnish-dev mailing list
varnish-dev@projects.linpro.no
http://projects.linpro.no/mailman/listinfo/varnish-dev
