very slow scans

[Paul <li...@pote.com>]

Hi -

I'm running SA version 3.4.4 on a Synology NAS/server (which runs a 
fairly limited Linux install) with 1G of RAM, using its basic 
spamd/spamc setup. I have network tests and Bayes temporarily disabled, 
and no custom rules, and my RAM and CPU are both under 15% average. 
Everything else on the machine is quick and responsive.

But it usually takes SpamAssassin over 100 seconds to scan a message, 
sometimes 300 seconds or more. I added a Timing header which reports 
that about 80% of that time is read_scoreonly_config. The nature of the 
message doesn't seem to make a difference.

It's been like this for a while, but I only just became impatient and 
decided to fix it.

Any tips on how to track this down? Thanks!

 	Paul

Re: very slow scans

["Kevin A. McGrail" <km...@apache.org>]

On 6/25/2020 4:13 PM, Paul wrote:
> I'm running SA version 3.4.4 on a Synology NAS/server (which runs a
> fairly limited Linux install) with 1G of RAM, using its basic
> spamd/spamc setup. I have network tests and Bayes temporarily
> disabled, and no custom rules, and my RAM and CPU are both under 15%
> average. Everything else on the machine is quick and responsive.
>
> But it usually takes SpamAssassin over 100 seconds to scan a message,
> sometimes 300 seconds or more. I added a Timing header which reports
> that about 80% of that time is read_scoreonly_config. The nature of
> the message doesn't seem to make a difference.
>
> It's been like this for a while, but I only just became impatient and
> decided to fix it.
>
> Any tips on how to track this down? Thanks!
Can you replicate the issue on the command line with spamassassin -t -D
< email.msg  and then with spamc?

-- 
Kevin A. McGrail
KMcGrail@Apache.org

Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171