Speeding up Spam Assassin

[Michael Coburn]

On my Debian stable / qmail P2 333 with 128M of ram and approximately 50
messages per hour, the average message requires 3 - 5 seconds to process
through spamc, and sometimes as long as 70 seconds.

Is it possible that your system is underpowered, or you have a busy MTA
with multiple messages being processed by spamc concurrently?
--
michael

On Wed, 2004-08-04 at 16:41, jim ruxton wrote:
> Hi,
> 
> > Hi Jim.  Spamc/spamd uses the same ruleset as the spamassassin perl script
> > by default.  I think this is unnecessary duplication. 
> Strange thing is spamassassin does catch the odd spam that spamc misses.
> I'm not sure why this is. Is it typical for spamc to take so long to
> analyze a message. Sometimes it even takes up to 30 seconds.
> jim
> >  Of course
> > spamc/spamd could be configured differently to spamassassin but that
> > really would be unnecessary complexity in most cases.
> > 
> > > anything spamc misses. It takes about 10-15 seconds per message
> > > sometimes for spamc to determine whether a message is spam. Any
> > > suggestions how I can speed this up?
> > 
> > Ordinarily I'd recommend spamc/spamd over spamassassin as they are so much
> > faster but you are already using using spamc/spamd.
> > 
> > So I'd say drop spamassaassin as a follow-up to spamc/spamd.
> > 
> > Cheers,
> > 	Rob
> 
> --
> The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
> TLUG requests: Linux topics, No HTML, wrap text below 80 columns
> How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml
--
The Toronto Linux Users Group.      Meetings: http://tlug.ss.org
TLUG requests: Linux topics, No HTML, wrap text below 80 columns
How to UNSUBSCRIBE: http://tlug.ss.org/subscribe.shtml