James Lay wrote: > > So my upgrade of Spamassassin takes a full five minutes to -D --lint > and about the same time to load up. Here's my local.cf file: > > required_score 4.0 > rewrite_header Subject *****SPAM***** > report_safe 0 > use_bayes 1 > use_bayes_rules 1 > bayes_auto_learn 1 > skip_rbl_checks 0 > ok_locales en > pyzor_options --homedir /etc/mail/spamassassin > > I have a BUNCH of SARE rules..however this didn't seem to impact the > previous version. Is this normal? > No it's not normal..
Purely stock SA 3.2.0 on an Athlon 64 3200+ comes back: #time spamassassin -D --lint real 0m2.569s user 0m2.336s sys 0m0.172s So some questions: - have you run spamassassin --lint, without the -D? Did it have anything to say? (9 times out of 10, folks overlook errors amidst the ton of debug, so I advise against using -D unless you have other reasons to do so) - when you run spamassassin -D --lint, are there any conspicuously long pauses? What debug lines come after the pause? - How much is a "BUNCH", roughly speaking? (to some folks a BUNCH would be 200+ .cf files occupying 30mb+ of disk space, others it would be 10 files totaling 512k) - Any non rulesemporium.com rulesets? any rulesets that NOBODY should be using unless they've got >10GB of ram, ie: sa_blacklist or sa_blacklist_uri? - Any redundant rulesets? ie: sc_top200 when you have network tests enabled, any *_x30.cf or *_x31.cf files (built into SA)? Also, for comparison, I ran a test with every non-redundant rulesemporium.com ruleset I could find: 70_sare_adult.cf 70_sare_obfu3.cf 70_sare_bayes_poison_nxm.cf 70_sare_obfu4.cf 70_sare_evilnum0.cf 70_sare_obfu.cf 70_sare_evilnum1.cf 70_sare_oem.cf 70_sare_evilnum2.cf 70_sare_random.cf 70_sare_genlsubj0.cf 70_sare_ratware.cf 70_sare_genlsubj1.cf 70_sare_specific.cf 70_sare_genlsubj2.cf 70_sare_spoof.cf 70_sare_genlsubj3.cf 70_sare_stocks.cf 70_sare_genlsubj4.cf 70_sare_unsub.cf 70_sare_genlsubj_eng.cf 70_sare_uri0.cf 70_sare_header0.cf 70_sare_uri1.cf 70_sare_header1.cf 70_sare_uri2.cf 70_sare_header2.cf 70_sare_uri3.cf 70_sare_header3.cf 70_sare_uri4.cf 70_sare_header_eng.cf 70_sare_uri_eng.cf 70_sare_header_x31.cf 70_sare_whitelist.cf 70_sare_highrisk.cf 70_sc_top200.cf 70_sare_html.cf 72_sare_bml_post25x.cf 70_sare_html_eng.cf 72_sare_redirect_post3.0.0.cf 70_sare_obfu2.cf 99_sare_fraud_post25x.cf #time spamassassin -D --lint real 0m4.081s user 0m3.728s sys 0m0.288s So even the SARE rules, in and of themselves shouldn't be a problem. However, adding sa-blacklist really changes things, spamassassin explodes to 500+mb in size and: #time spamassassin -D --lint real 0m53.189s user 0m41.127s sys 0m1.568s
