high iowait

Sean Allen sean at monkeysnatchbanana.com
Wed Mar 20 02:46:37 CET 2013

One of our varrnish servers is spending about 40-50% of its time in iowait.
Is this just from the varnishlog getting written? Our IO performance is not
great and I'm looking to be able to get the amount of time we are spending
doing IO down. This occurs even when everything is running nicely in memory
and we aren't overflowing into swap ( which was detailed in a different
email as I think they might be different issues ).

varnishd (varnish-3.0.3 revision 9e6a70f)


# -*- mode: conf-unix -*-
# Configuration file for varnish
# This file is managed by puppet.
# Local changes will be reverted.
# /etc/init.d/varnish expects the variable $DAEMON_OPTS to be set from this
# shell script fragment.

# Maximum number of open files (for ulimit -n)

# Locked shared memory (for ulimit -l)
# Default log size is 82MB + header

# Maximum size of corefile (for ulimit -c). Default in Fedora is 0

# Listen on port 6081, administration on localhost:6082, and forward to
# one content server selected by the vcl file, based on the request.  Use a
# fixed-size cache file.
# Without "ban_lurker_sleep," nothing banned from the cache ever gets
DAEMON_OPTS="-a :6081 \
             -T :6082 \
             -f /etc/varnish/default.vcl \
             -u varnish -g varnish \
             -p thread_pool_min=500 \
             -p thread_pool_max=5000 \
             -s malloc,6G \
             -p thread_pools=2 \
             -p thread_pool_add_delay=1 \
             -p ban_lurker_sleep=60s"


Ce n'est pas une signature
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.varnish-cache.org/lists/pipermail/varnish-misc/attachments/20130319/28a8339c/attachment.html>

More information about the varnish-misc mailing list