Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 8 Jul 2003 00:22:33 +0100
From:      Daniel Bye <dan@slightlystrange.org>
To:        freebsd-questions@freebsd.org
Subject:   Re: spamassassin slow to process messages
Message-ID:  <20030707232232.GA82782@catflap.home.slightlystrange.org>
In-Reply-To: <1057619317.52026.28.camel@athomson.prv.au.itouchnet.net>
References:  <1057619317.52026.28.camel@athomson.prv.au.itouchnet.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--opJtzjQTFsWo+cga
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Jul 08, 2003 at 09:08:37AM +1000, Andrew Thomson wrote:
> I'm looking for some suggestions as to why my spamassassin is so slow!
>=20
> Installed from ports.
>=20
> Details:
>=20
> p5-Mail-SpamAssassin-2.55
> 5.0-RELEASE-p7
>=20
> I'm running spamd and using spamc/procmail to pass the messages to
> spamd.
>=20
> I was reading the following,
>=20
> http://spamassassin.rediris.es/dist/spamd/README.spamd
>=20
> and it was talking with figures like:
>=20
> "Well, on my 400MHz K6-2 mail server, spamassassin process a 11689 byte
> message in about 3.36 seconds, spamc/spamd processes the same message in
> about 0.86 seconds, or about 4 times faster."
>=20
> I've got a CPU: Pentium III/Pentium III Xeon/Celeron (930.32-MHz
> 686-class CPU) and I'm seeing performance like,
>=20
> Jul  8 08:25:11 athomson spamd[52016]: clean message (0.4/5.0) for
> ajt:1001 in 10.2 seconds, 2132 bytes.=20
> Jul  8 08:25:27 athomson spamd[52031]: clean message (0.4/5.0) for
> ajt:1001 in 10.2 seconds, 2092 bytes.=20
> Jul  8 08:30:12 athomson spamd[52074]: identified spam (16.0/5.0) for
> ajt:1001 in 10.3 seconds, 3158 bytes.=20
> Jul  8 08:30:28 athomson spamd[52093]: clean message (-2.1/5.0) for
> ajt:1001 in 10.2 seconds, 2847 bytes.=20
> Jul  8 08:30:44 athomson spamd[52100]: clean message (0.4/5.0) for
> ajt:1001 in 10.2 seconds, 2133 bytes.=20
>=20
> Much smaller messages, taking much longer to process!!

Could be mx timeouts, DNS timeouts, rbl timeouts, dcc/razor/pyzor
timeouts...

In your global SpamAssassin config, try setting a value for timelog_path -
this will cause spamd to log what it's doing, and where it spent most time
doing it.  Check perldoc Mail::SpamAssassin::Conf.

You might also try turning on debugging (modify /usr/local/etc/rc.d/spamd.sh
so that spamd is called with the `-D' option, then restart spamd).  You will
then get lots of debugging in /var/log/mail.

HTH

Dan

--=20
Daniel Bye

PGP Key: ftp://ftp.slightlystrange.org/pgpkey/dan.asc
PGP Key fingerprint: 3B9D 8BBB EB03 BA83 5DB4 3B88 86FC F03A 90A1 BE8F
                                                                     _
                                              ASCII ribbon campaign ( )
                                         - against HTML, vCards and  X
                                - proprietary attachments in e-mail / \

--opJtzjQTFsWo+cga
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)

iD8DBQE/CgC4hvzwOpChvo8RAprnAJwKRlmgyeSGsye5HllrrpDpRpc6DwCeIP2b
ti66Fgk5ut8btQ8tnYKjxus=
=cOj8
-----END PGP SIGNATURE-----

--opJtzjQTFsWo+cga--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030707232232.GA82782>