On 2016-06-09 12:05 PM, Cristian Mammoli ([email protected]) wrote:
ProxyPass /Microsoft-Server-ActiveSync \
http://srvsogo02.apra.it:20000/SOGo/Microsoft-Server-ActiveSync \
retry=60 connectiontimeout=5 timeout=360
and sogo.conf:
/* ActiveSync */
SOGoMaximumSyncResponseSize = 1024;
SOGoMaximumPingInterval = 10;
SOGoMaximumSyncInterval = 30;
SOGoInternalSyncInterval = 60;
These settings are broken. Reread:
https://sogo.nu/files/docs/SOGoInstallationGuide.html#_microsoft_enterprise_activesync_tuning
WOWorkersCount = 40;
SxVMemLimit = 384;
From the tests I did I cannot set WOWorkersCount lower than 40 or I
start getting lots of:
No child available to handle incoming request!
I cannot set lower than 384 either: I already have lots of:
terminating app, vMem size limit (384 MB) has been reached
(currently 397 MB)
That is normal - as what is considered right now, is the VSZ value -
which can be quite large, especially on 64-bit systems. I think we
should rather consider the RSS value, which can be more easily tuned and
understood.
The server has 4 cpus and 12 GB of RAM and after only 6-8 hours all
the RAM is occupied and the server start swapping until the oom killer
terminates all sogod processes.
I have another server with 4 GB of RAM that is handling 200 heavy
Thunderbird clients just fine.
Is this expected behaviour? How many resources am I supposed to use to
handle 90 phones?
If you have 90 phones, you should have at least 90 sogod processes since
an EAS connection using push will consume one process. You can even
dedicate a sogod instance for EAS
(https://sogo.nu/nc/support/faq/article/dedicated-separate-sogo-instance-for-activesync.html)
EAS sogod processes will generally consume 16 to 50 MB of RSS.
Thanks,
--
Ludovic Marcotte
[email protected] :: +1.514.755.3630 :: http://inverse.ca
Inverse inc. :: Leaders behind SOGo (http://sogo.nu), PacketFence
(http://packetfence.org) and Fingerbank (http://fingerbank.org)
--
[email protected]
https://inverse.ca/sogo/lists
