-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jerry Glomph Black writes: > spamd 3.0 does preforking of the child processes. > > Nothing wrong with that, but WHY do the children have such enormous RSS > numbers already when started (>20 Meg per process)? To me, this makes > no sense. > > 3.0 has rendered two decent machines of mine useless by snarfing up all > the RAM. > > Can this be put back to the old fork-on-demand model? I'm convinced > that the current forking scheme is broken. > > Is the old 2.6x spamd code compatible enough to run with all the 3.0 > perl apparatus? most of this memory is shared. spamd preloads as much as possible upfront, to maximise memory sharing -- including all the rules, compiled into perl code etc. recent investigation (can't recall bug #) is showing that this is working, too... - --j. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Exmh CVS iD8DBQFBYi4oQTcbUG5Y7woRAvODAKDiWxNLCaKaBCf+61/Yfd2z7hbGTACcDQSU aNq6h+LAU/vLNcqu9bRuHlo= =h/kR -----END PGP SIGNATURE-----
