-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jon Trulson writes: > On Sat, 6 Nov 2004, Justin Mason wrote: > > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > > > Scott writes: > >> I did realize I had big evil running.. Which by removing that it cut my > >> memory usage to 42MB per child.. What is the recommended replacement for > >> big evil? Is it already part of 3.0.1? > > > > SURBL. Support for it is builtin to 3.0.x by default. > > > > All the people who are reporting massive memory usage on 3.0.x, please > > try *without* add-on rulesets. 42MB is still about twice the normal > > memory usage on an x86 platform, and that's all rules, if it's that > > size just after startup. > > > > FWIW, I use no custom rulesets with v3 currently. At least on my > system, the memory issues had nothing to do with a custom ruleset or 3. > > The --max-children=1 flag to spamd has 'solved' the issue for > me... Average child size is around 19-20MB, until 'the event' happens, at > which point it jumps to around 320MB. I'm considering writing some scaling code so that spamd starts with 1 server, and scales up to max-children if the existing number of servers is overloaded. That would probably help for the cases where - --max-children=1 helps, which seem to be a lot of them. - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFBmXJzMJF5cimLx9ARAtB1AJ9lMUIzQroxKLLsPnP/GK5lp4mffgCeKVO4 5PyCpr4IbEEAdFaWHdrpLIM= =gBdP -----END PGP SIGNATURE-----