Simple, start spamd with a max child limit ( -m ## ) to keep it out of swap. Start with 10, monitor your memory and increase/decrease if needed.
> -----Original Message----- > From: Ross Kramer [mailto:[EMAIL PROTECTED] > Sent: Monday, May 24, 2004 4:54 PM > To: [EMAIL PROTECTED] > Subject: Load limiting spamd > > Got an interesting problem... > > I am running spamd in a client/server config... ie spamd runs remotely > on a separate system from my client system that is running sendmail. The > performance gain is decent, problem is if too many spamd connections are > made, spamd eats its host box for breakfast. This wouldn't be an issue > if I was running spamd on the same machine as sendmail/spamc since > sendmail has the ability to load-limit... ie, refuse connections if it > is at a certain loadavg, but the through-put sucks. What I need is to > make spamd smart enough to put on the brakes if it is too busy. Anybody > have any ideas as to how to accomplish this? > > --R > > "It is by caffeine alone I set my mind in motion, > It is by the beans of Java the thoughts acquire speed, > the hands acquire shakes, > the shakes are a damn nuisance, > It is by caffeine alone I set my mind in motion." > -- The Liturgy of Caffeine
