site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Nathan, -Andrew _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On Jan 29, 2009, at 4:29 PM, Nathan wrote: As I stated earlier, it just uses lots of processes, so as soon as we were able to discover that and raise the process limits in the kernel and launchd, all our severe problems disappeared. I believe that Cyrus has a "maxchild" option that limits the number of processes it uses internally. I'm curious, what is the behavior of Cyrus if you limit it to a few hundred processes in this environment? That seems pretty common based on the conf files that I found with Google, and I would expect Cyrus is capable of handling a few hundred users with a few hundred processes as long as it knows that it can't make more. Is that not the case? Three processes per Mail.app user seems like an awful waste otherwise. Being a kernel engineer, however, my knowledge of IMAP servers is rather limited. Does Cyrus start rejecting connections in that case? Or is performance just unacceptable? This email sent to site_archiver@lists.apple.com