Rosenbaum, Larry M. wrote:
Running SpamAssassin v3.2.0 on Solaris 9, perl v5.8.8.
I am getting really poor performance with v3.2.0 compared with v3.1.8.
Average scan time per message is doubled (or worse). I’m also seeing
messages like this in the log file (although not all the time):
Trying running with debug enabled so that you can see what's holding
things up.
Does running with -L (local test only) complete quickly?
May 7 17:10:20 localhost spamd[19457]: plugin: eval failed: child
processing timeout at /usr/local/bin/spamd line 1259, <GEN390> line 377.
Bayes auto expiries (taking to long and getting killed)? I think that's
a 600 second timeout.
Is there any way to tell what the timeout was waiting for, or why
performance has gotten worse? I haven’t changed the rules.
Run with debug enabled.
Daryl
