> It happend, because you didn't have enough workers for the rush. > For such rush traffic you also could increase WOListenQueueSize. > This tells sogod to queue up that count of requests for its workers. > This will not decrease your workload, but clients are not rejected > instantly, when no worker is available. > > You do not need to kill those workers by yourself. > Instead you can decrease WOWatchDogRequestTimeout (in minutes) which is > set to 10 minutes by default. > Then the SOGo WatchDog will kill those processes for you. > > Your RAM should be approx.: > worker count * SxVMemLimit (which is in MB) > > In your case 20 * 384 MB = 7680 MB (~ 8GB) > > With 20 workers you should be able to handle all 200 users, as long as > they use web interface and/or calDAV/cardDAV. > > If you have ActiveSync users, you have to reserve one worker per > ActiveSync connection! > > > Kind regards, > Christian Mack >
Thank you, Christian, for these valuable pointers personalized for my situation. I am now confident in my ability to adjust the configuration to accommodate users both existing and new. Your help is greatly appreciated, Josef -- [email protected] https://inverse.ca/sogo/lists
