Question about varnish memory usage
Dridi Boukelmoune
dridi.boukelmoune at zenika.com
Thu Sep 18 16:50:56 CEST 2014
On Wed, Sep 17, 2014 at 7:58 PM, Adam Schumacher
<adam.schumacher at flightaware.com> wrote:
snip
>
> Varnishd is configured as follows in rc.conf:
>
> varnishd_storage="malloc,6G"
> varnishd_opts="-p send_timeout=200 -p sess_timeout=4 -p
> thread_pool_max=4000 -p thread_pool_add_delay=3 -p thread_pools=24 -p
> thread_pool_min=33 -p listen_depth=4096 -p thread_pool_add_delay=2 -p
> ping_interval=2 -h classic,250007 -p connect_timeout=2 -p cli_timeout=15
> -p sess_workspace=262144"
>
> varnishd_flags="-P /var/run/varnishd.pid -a ${varnishd_listen} -f
> ${varnishd_config} -T ${varnishd_telnet} -s ${varnishd_storage} -u
> ${varnishd_user} -g ${varnishd_group} ${varnishd_opts}"
Hi Adam,
thread_pool_max=4000
thread_pools=24
sess_workspace=262144
IIRC it means up to 4000x24x262144 bytes of RAM (about 24Go) *only*
for worker workspaces.
Probably not what you want.
thread_pool_add_delay=3
thread_pool_add_delay=2
It looks like your tuning needs some love.
Cheers,
Dridi
More information about the varnish-misc
mailing list