http://bugzilla.spamassassin.org/show_bug.cgi?id=3983
------- Additional Comments From [EMAIL PROTECTED] 2004-11-23 13:46 ------- the MaxClients thing won't be a problem for us I don't think. by default that remains at 5, and users would have scaled that by now if they ran into low-RAM situations with 3.0.x. I also added a warning about that. (MaxClients == --max-children in SAland) I think the patch matches up with what Dean notes; it'll generally run with 1 kid, 2 if there's mail active, and scales up to 5 if things get really busy, by default. this patch works a *lot* better, in many ways, btw -- check out what it looks like on my server after running for nearly a day: 29880 root 17 15 22248 5244 4276 S N 0.0 1.0 0:03 spamd 11505 root 17 15 65336 60M 7180 S N 0.0 12.0 0:44 spamd 28823 root 17 15 29872 25M 7204 S N 0.0 5.1 0:03 spamd ie. the master proc has only 5MB paged in while still having all the code and modules preloaded and precompiled, that's very nice; the subprocs have scaled their RAM usage based on size of messages coming in; there's only two subprocs; and one of those (the big one) is the one handling all the messages, with the second having handled only a small amount of overflow, based on the CPU times. that all looks very good. (note however I don't think the reported SHR values are correct on that kernel as mentioned in prev bugs, so ignore those.) ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
