Justin Mason wrote: > > jdow writes: > >>>You are using larger chunks of VIRT than I am. I use about 60M where >>>you are using 98M. I run with "--max-conn-per-child=15". You win a >>>little if you either add RAM or cut down to "-m2" or "-m3". You do >>>have a fair amount of cache in use. Once that happens you flounder >>>around in cache swapping when running spamassassin. > > > the fundamental problem is that he's not using spamd.
Well, that's about 3/4 of his problem Justin. The other 1/4 is he's also got a massively oversized configuration with duplicate rulesets, and large unsupported rulesets like bigevil. Switching to spamd would help him in speed, and will limit the memory usage by limiting the number of children, but the per-child memory usage will still be high until he gets rid of bigevil. > > rule of thumb: if you see performance issues, and you're not using > spamd, STOP RIGHT THERE and start using spamd ;) Unless you're using some other persistent daemon for integration that uses the Mail::SpamAssassin API, such as MailScanner or similar. (note: just using Mail::SpamAssassin in a perl script that gets called for each message as the OP is doesn't count. It's got to be a persistent daemon that doesn't get re-invoked for every message in order to be comparable to spamd.)
