-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Ralf Hildebrandt writes: > I'm using spamassassin from within amavisd-new. Loggin shows that > amavis's SA-check is the most time-consuming step while processing an > email (>>80% of the total time needed). > > How can I run spamassassin against some mails to find out what part of > spamassassin (maybe some sort of external DNS query) takes how much > time? > > I was thinking of a sort of "profile" (subrouting x takes y seconds) > to find out where my particular installation of SA is "slow". perldoc Devel::DProf -- that's the perl profiler. but as you said, it now appears to be bayes -- it could be that if a scan is taking a *very* long time, what's actually taking place is a Bayes expiration run, which happens once every N days (typically). Run spamassassin with -D (debugs) to see if that's it. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFBPz67QTcbUG5Y7woRAj7RAKCvYhL6zjakFVZUF18RdtTc4WMdHACcDwzN nX1/6vVWqerMhcOCdcX/lNg= =SGCj -----END PGP SIGNATURE-----
