http://www.hughes-family.org/bugzilla/show_bug.cgi?id=129
Summary: Ideas for optimization..
Product: Spamassassin
Version: 2.11
Platform: Other
OS/Version: FreeBSD
Status: NEW
Severity: enhancement
Priority: P2
Component: spamassassin
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
You may already be doing this, but a few ideas for optimization:
Presently SA is relatively
slow and a big resource hog. It's spam catching performance however, is awesome and
outweighs the
performance problems.
1) certain rules may trigger an immediate bailout, such as
whitelist, blacklist, etc. These rules should always be processed first.
2) process all
negative rules next.
3) process all "most common" or else "highest scoring" rules next.
Whichever heuristic you go with depends on which performs better. "Most common"
requires you
determine which rules are most likely to get triggered the most often. "Highest
scoring" might
work since when these rules are triggered they almost always indicate a spam hit.
4) bail out
of step #3 above as soon as the spam threshold is exceeded.
Perhaps you are doing something
like this already? Please let me know.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Spamassassin-talk mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
