On Wed, Sep 23, 2009 at 2:58 PM, Jari Fredriksson <ja...@iki.fi> wrote: > > > Dear Sirs, > > > > So runs Spamd > > > >>> states: BBBBBBBBBBBBBBBBBBBB > > > > /usr/bin/spamd -v -u vpopmail -m 20 -x -q -s stderr -r > > /var/run/spamd/spamd.pid > > > > If I have about 10,000 emails to have less processes > > SpamD (Example 5) did not cause problems? > > > > Thanks > > > > Jose Luis > > > Well 10000 is what I get in a month, so I'm no expert. > > But if you put too many processes for your hardware to maintain, there will > be problems, because they will just trash the system and not run. > > If you try with 5, everything will run, and the email will grow the queue. > Nothing will be lost. > > But with -m 20 I'm afraid something will eventually be lost as the system may > crash. > > 10000 mails in queue... Maybe you need a farm of those machines. SpamAssassin > can do that.
Yes this looks like the problem. Reduce the # of processes to fit within ram and the machine can handle much more mail. Look at how much ram each one uses and adjust so that you have as many as possible without swapping. Sounds like 5 would be a good place to start. Its no problem to have some mails in the queue, more important is the time any one message spends there, or if the queue continues to grow. 10k in queue is not too bad as long as the number starts dropping after proper adjustment of SA instances. A lot of the time SA spends with a message is just idling waiting on network checks to finish. A local caching nameserver can speed this up. do you use one? probably worth the ram it takes away from SA. Once you limit the # of instances to work within the available RAM, see if the delay is reasonable. good luck -Aaron
