Turns out I sent this email too soon. Even though I have use_pyzor 0 in my local.cf, having these lines in v310.pre uncommented was causing the 5 seconds extra scan time:
loadplugin Mail::SpamAssassin::Plugin::Pyzor loadplugin Mail::SpamAssassin::Plugin::Razor2 On Tue, Aug 31, 2010 at 10:51 AM, Sean Kennedy <skenn...@office.vcn.com> wrote: > I'm running SpamAssassin v3.3.1. A message with 500 lines of text > (22k) is taking 6-7 seconds. > > This is using spamc. I am using a Bayes DB (no auto expire/learn) > that's stored in SQL. User preferences are also stored in SQL. I > have skip_rbl_checks on. I am using only the official rules from > updates.spamassassin.org and I am using sa-compile. > > I've also disabled all of these rules: > > score URIBL_SBL 0 > score URIBL_SC_SURBL 0 > score URIBL_PH_SURBL 0 > score URIBL_AB_SURBL 0 > score URIBL_JP_SURBL 0 > score URIBL_OB_SURBL 0 > score URIBL_WS_SURBL 0 > score URIBL_BLACK 0 > score URIBL_RED 0 > score URIBL_GREY 0 > > I tried disabling Bayes checks as well. The message still took > 5.5-6.5 seconds to finish scanning. I'm testing scan time using: > > time spamc -E -u skenn...@office.vcn.com < ./testmail.txt > > The server I am testing this on is a AMD Athlon(tm) 64 X2 Dual Core > Processor 3800+ w/ 2GB of memory. I am testing this while the server > is otherwise idle. > > > Does anyone have any other ideas what could be causing this to go that > slow? I would expect 1s or less for a plain-text 22k message. > > Thanks, > Sean >
