* MSGMNB and MSGMAX: good default values?
@ 2014-05-31 17:54 Manfred Spraul
0 siblings, 0 replies; only message in thread
From: Manfred Spraul @ 2014-05-31 17:54 UTC (permalink / raw)
To: Linux API, Linux Kernel Mailing List, Michael Kerrisk,
Davidlohr Bueso
Hi all,
until now, every sysadmin/distro had to update the sysv limits.
For shm, the new proposal is to increase the limits to (nearly) ULONG_MAX.
Right now, I try to create patches that also increase the limits for
sysv msg, but I got stuck:
- MSGMNI is trivial, just increase it to nearly IPCMNI.
- MSGMNB is not an upper limit, it is actually the default amount of
data that can be stored in a message queue before senders must sleep.
Since Linux-0.99.10, it always was 16384.
A websearch shows that for both db2 and oracle, the recommendation is
65536.
It seems that redhat has increased the value to 65536:
https://bugzilla.redhat.com/show_bug.cgi?id=862597
Tuxedo seems to use sysv messages and the documentation warns that too
large values are harmfull:
http://read.pudn.com/downloads142/doc/618733/tux-a11-80/manual/13-ADM-PERF-Notes.pdf
- MSGMAX: Same issue as above: it was slightly below 4096 and since 2.6
it is 8192.
Any proposals?
Right now, I would leave MSGMAX and MSGMNB as they are.
--
Manfred
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2014-05-31 17:54 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-05-31 17:54 MSGMNB and MSGMAX: good default values? Manfred Spraul
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.