The machine has 16G Munin complains like: N worker threads not created is 4.33 Even on sustained high traffic, for half an hour for instance, it will always max out on 1024 threads. The munin graphs always flat out at this point.
On 15 nov. 2011, at 09:51, Cosimo Streppone wrote: > On Mon, 14 Nov 2011 19:38:44 +0100, Arjen Schat <[email protected]> wrote: > >> This is the config used for startup. > > Please send emails to the list. > >> # Maximum number of open files (for ulimit -n) >> NFILES=131072 >> >> [...] >> >> DAEMON_OPTS="-a 219.201.78.31:80 \ >> -T 168.20.2.106:6082 \ >> -f /etc/varnish/default.vcl \ >> -p listen_depth=4096 \ >> -p session_linger=150 \ >> -p thread_pool_add_delay=5 \ >> -p thread_pools=4 \ >> -p thread_pool_max=1500 \ >> -p thread_pool_min=50 \ >> -u varnish -g varnish \ >> -S /etc/varnish/secret \ >> -s malloc,6G" > > How much memory do you have in your system? > An idea would be to check syslog for varnishd messages. > > Also check varnishstat for the "N worker threads limited" counter. > That gives you an idea of how many and how quickly varnish tries > to create threads but doesn't succeed, IINM. > > -- > Cosimo > > _______________________________________________ > varnish-misc mailing list > [email protected] > https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc _______________________________________________ varnish-misc mailing list [email protected] https://www.varnish-cache.org/lists/mailman/listinfo/varnish-misc
