Ulimits and varnish - should I increase?
Harri.Paivaniemi at tieto.com
Harri.Paivaniemi at tieto.com
Thu Aug 4 15:11:38 CEST 2011
Hi all,
I'm starting to use varnish with a customer who has about 20 000 http req/s.
I'm trying to figure out if I need to increase ulimits for varnish-user or not (RHEL 6 64bit). In varnish-conf there is this default:
--
# Maximum number of open files (for ulimit -n)
NFILES=131072
# Locked shared memory (for ulimit -l)
# Default log size is 82MB + header
MEMLOCK=82000
# Maximum size of corefile (for ulimit -c). Default in Fedora is 0
# DAEMON_COREFILE_LIMIT="unlimited"
---
So, What are those NFILES,MEMLOCK and DAEMON_COREFILE_LIMIT doing... I mean that obviously those are not enough to raise those limits in the system? Should I put to security/limits-conf those values for varnish-user or to sysctl for all?
Thanks very many.
-hjp
This is my ulimit now:
[root at fihgac4devproxy ~]# ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 30527
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 1024
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
More information about the varnish-misc
mailing list