Hi ! Thank you for your tip.
The problem here is that each process grows over the SxVMemLimit. So even one single sogod process will bring the server to it's knees. It is as if SOGo ignores this parameter. MVH Sigurd Holter Bookingleder/prosjektleder West Audio A/S Consul Sigval Bergesens vei 41 4014 Stavanger Tlf. 51537030 <div>-------- Opprinnelig melding --------</div><div>Fra: Martin Simovic <[email protected]> </div><div>Dato:11.11.2014 15:26 (GMT+01:00) </div><div>Til: [email protected] </div><div>Emne: Re: [SOGo] ActiveSync ignores SOGoMaximumSyncWindowSize and eats all RAM/swap </div><div> </div>I believe that you should have only as much SOGo processes available (prefork=X) that multiplied by SxVMemLimit <= amount of RAM available on your server. M. -- Martin Šimovič NETSON s.r.o. Mlynská 1/2338 934 01 Levice tel: +421 915 393 570 mail: [email protected] On 11 Nov 2014, at 15:17, Sigurd Holter <[email protected]> wrote: Hi ! It seems that Outlook 2013 connection to a huge mailbox makes SOGo eat all available RAM and swap. I tried setting SOGoMaximumSyncWindowSize to 50 (down from 200), but it doesn't seem to make any difference. SxVMemLimit is set to 2 GB, but the processes easily reach 16GB - then I have to kill them off. I also tried deleting the Outlook profile (both files and from registry) and start from scratch. Didn't make a difference. Restarted SOGo, restarted memcache - no difference. Is there a settings cache or similar that needs to be cleared in SOGo ? -- MVH Sigurd Holter Bookingleder/prosjektleder West Audio A/S Consul Sigval Bergesens vei 41 4016 Stavanger Telefon 51537030 -- [email protected] https://inverse.ca/sogo/lists -- [email protected] https://inverse.ca/sogo/lists
