Hello

PREFORK is overwriting WOWorkersCount, therefore the latter is
irrelevant, as long as you don't start the sogod Process by hand (e.g.
for debugging).
You would need to set Prefork to 1800.

You RAM is not sufficient for that many workers.
You need  a minimum of 16 up to 50 MB for each ActiveSync Client:
1500 * 16 MB = 24 GB
Plus your RAM for the 300 concurrent web and calDAV/cardDAV users:
We use 32 GB for 350 concurrent user, which is enough, but not plenty.

Therefore it is no surprise to me, that your sogod does not start with
only 16 GB RAM.


Do you have a support contract with Inverse?
In my experience they respond fast if you have one, especially Ludovic.


Kind regards,
Christian Mack

Am 05.01.2018 um 19:58 schrieb Karl Hoffner
([email protected]):
> As mentioned, when PREFORK is greater than 500, the service will not start. 
> My server CPU average is about 5% and memory is about 60% with 0.4% swap. I 
> can easily add more memory, but performance wise, we are barely touching the 
> allocated specifications.
> 
> Regards,
> Karl
> 
> From: [email protected] [mailto:[email protected]] On Behalf Of Bruno 
> CAPELETO
> Sent: Friday, January 5, 2018 11:36 AM
> To: [email protected]
> Subject: Re: [SOGo] Performance Issues
> 
> 
> As far as I know, you need one sogo prefork for every single EAS client.
> 
> Every sogo prefork needs some ram...
> 
> 
> 
> 2018-01-05 16:26 GMT+01:00 Karl Hoffner <[email protected]>:
> We have a single instance iRedmail/iRedAdmin-Pro/MySQL/SOGo instance running 
> on CentOS. We initially started the server with about 40-50 mailboxes and 
> users and had little or no issues. We recently added about 1500 mailboxes 
> with 1500 users. All users will be using EAS - thus the need for SOGo and 
> ActiveSync. Since the addition of the users we cannot use the SOGo web 
> interface or iRedAdmin-Pro unless we restart the sogod service. This is 
> required about every couple minutes. Sometimes as little as 60 seconds and in 
> off hours, perhaps up to 5-6 minutes.. I did create a restart fiunction to 
> restart the service every 5 minutes. This was not working as we still were 
> unable to access. So we had it down to 2 minutes. This helped, but if you 
> were sending message at that time, it would fail and you would have to 
> rewrite.
> 
> We have made changes to the PREFORK (initial default at 3), increase to 30, 
> then increased to 50, then 100; now at 500. (Larger numbers than 500 prevent 
> sogod from starting)
> We also had to up the SQL max_connections to 700  to function.
> We increased the WOWorkersCount to 500 then to 1800 (1500 EAS + 20%)
> We tried moving EAS to a new port and spawning  its own process using the 
> instructions in the following link; the new service will not start indicating 
> the port is in use.
> https://sogo.nu/nc/support/faq/article/dedicated-separate-sogo-instance-for-activesync.html
> Using ps -A, only one instance is using 127.0.0.1:20000 and none on 30000 as 
> per the instructions. Apparently the GNUstepDefaults file is not being read?? 
> Anyway, this failed and we still basically have an unusable email server.
> 
> Any help would be welcome as we requested professional support from SOGo with 
> no contact back. If we cannot resolve, we will be forced to find an 
> alternative as the performance for this many users is unacceptable. I was and 
> am hoping to not have to waste the time to recreate a new mail server.
> 
> CentOS: 7.36.1611 w/8 CPU and 16 GB memory
> iRedmail 0.9.6 MARIADB edition
> iRedAdmin-Pro 2.6.0
> 
> Regards,
> Karl
> 
> 
> CONFIDENTIALITY NOTICE: This electronic mail transmission and any documents, 
> files, or previous e-mail messages attached to it may contain confidential 
> information and are solely for the use of the individual or entity to which 
> they were intended. If you have received this message in error, please notify 
> the sender immediately by e-mail, discard any paper copies, and delete all 
> electronic files of the message.
> --
> [email protected]
> https://inverse.ca/sogo/lists
> 


-- 
Christian Mack
Universität Konstanz
Kommunikations-, Informations-, Medienzentrum (KIM)
Abteilung Basisdienste
78457 Konstanz
+49 7531 88-4416

Attachment: smime.p7s
Description: S/MIME Cryptographic Signature

Reply via email to