|Main Archive Page > Month Archives > spamassassin-dev archives|
--- Comment #11 from Mark Martinec <Mark.Martinec@ijs.si> 2011-09-21 10:36:38 UTC ---
We still do not have a confirmation that the culprit is Bayes.
Marcin, please re-read what John Hardin has asked:
> I find it really difficult to believe that Bayes would cause scanning timeouts
> absent other factors. Can you provide debugging traces that show the timeout
> and include whatever indicators lead you to believe that the number of words
> is the causative factor?
We haven't seen the debug trace yet. The most important part of it
(assuming you are using SA 3.3.2, you haven't indicated a version in
the bug report ticket) is a timing breakdown report. You can restrict
debugging to timing only for starters, if you like:
spamassassin -t -D timing <test.msg
(the '-D timing' is applicable to spamd too, but let's start with the basics,
as you are saying that spamassassin takes about two minutes as well).
On our host the regular regexp rules tests on this sample message take
20 seconds and bayes takes 1 second.
-- Configure bugmail: https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.