Hello
Hi folks,
I'm getting this log message: terminating app, vMem size limit.
Aug 30 07:36:40 sogod [20709]: |SOGo| terminating app, vMem size limit (384 MB)
has been reached (currently 389 MB)
Using default value 384MB, should I increase this value on sogo conf?
It depends.
You will always get some of these log entries.
Worst case would be, that after every request SOGo starts a new worker.
You can reduce their number by increasing SxVMemLimit.
But you will also increase your RAM usage.
If you have enough RAM left even for peak load, then increase it.
We also have a lot (~500 a day) of these log messages on our server.
Maybe just recently, maybe for a longer time. Our settings are:
WOWorkersCount = "50";
WOListenQueueSize = "10";
WOWatchDogRequestTimeout = "60";
SxVMemLimit = "512";
Preceding lines before the child processes get terminated:
Apr 23 07:24:21 sogod [27093]: ... "GET
/SOGo/dav/user/Calendar/personal.ics HTTP/1.1" 200 49746/0 20.191 245196
79% 625M
Apr 23 13:17:26 sogod [16168]: ... "GET
/SOGo/dav/user/Calendar/personal.ics HTTP/1.1" 200 755747/0 7.949 - - 250M
Are these request sizes normal?
Am I right in the assumption, that child processes get occupied during a
request and afterwards get freed again? And with 50 workers * 512 MB
Memlimit wouldn't that in theory be 25 GB that could get used?
We have a few hundred daily users on the server, but the RAM is far from
full with 1,5-3 GB used of 8 GB. What are benchmark values of these
settings with our amount of users/RAM (excluding EAS users)?
Kind regards,
--
Thomas Winterstein .................... http://www.rz.uni-augsburg.de/
Universität Augsburg, Rechenzentrum ............. Tel. (0821) 598-2068
86135 Augsburg .................................. Fax. (0821) 598-2028
--
users@sogo.nu
https://inverse.ca/sogo/lists
