evolution/spamd childs/memory

[Justin Mason]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Maximilian Gerlach writes:
> Hi,
> does anybody know why evolution always has 5 spamd childs running which
> each take about 30mb of ram? This brings evolution to over 100mb of ram.
> Any way to reduce at least the number of the spamd processes?

FWIW, much of that RAM is shared (although the 2.6 kernel does not
report it as such).  but I agree, that's not a good situation anyway!

I'm not sure how it's exposed in evolution, or what process starts the
spamd -- but the "-m" switch to that command reduces the number of
children started.

For a single user, especially on a desktop machine, limiting spamd to
scanning 1 mail at a time would seem to make sense; -m 1.

SpamAssassin 3.1.0 includes Apache-style scaling preforking, where the
number of running children scales between a high and low water-mark
depending on load.  This is much less memory-hungry.

- --j.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Exmh CVS

iD8DBQFCHjh3MJF5cimLx9ARArFrAJ0fs+f3uXM7bqikBaaK03TnCEvlcACgmEI9
VDrVFsSYdl044gOhxOGJ7xY=
=Tl1x
-----END PGP SIGNATURE-----