Ruben Safir wrote:
On Wed, Aug 20, 2014 at 01:03:12PM +0200, Per Jessen wrote:
Carlos E. R. wrote:
spamd/spamc called from procmail takes 1..3 seconds per email in my machine, but often it goes up to 5 seconds per email (I see this in the log), and even more. This is due not to lack of cpu power, but for waiting for online tests to respond or timeout.
Yup.
[snip]
This is a big issue when you get a queue of a thousand emails. It can takes hours if you do one at a time.
Anyone with a lot of email will really want to run spamassassin in parallel - it takes up very little space/cpu because most of the time is spent waiting for the network (DNS queries).
(apologies if this has been mentioned earlier, I haven't followed the entire thread.)
The last time I used spam assassign, aside from pegging my CPU, and creating a huge database file, it also took forever to train.
If you're using Bayes, which is optional.
Admitedly, this was a long time ago, but I used to recomend that spam assassign be put on its own machine back then.
No real need - certainly not today with multiple cores and gigabytes of memory. I have a test system running spamassassin on a (set of) Pentium II 400MHz with 384Mb RAM. -- Per Jessen, Zürich (15.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org