Gary V wrote: > On 9/18/08, Len Conrad <[EMAIL PROTECTED]> wrote: > >> so now I've got 10 vscan's democratically eating 100% CPU with avg cpu load >> of 10, 100+ MB RAM available. >> >> spamd and clamav worker bees still doing nearly 0% wcpu. >> >> Still doesn't seem right that amavis as an interface should be eating the >> entire machine while the content-scanners basically are idle. >> >> iostat still shows many seconds of 0 bytes disk i/o. >> >> Len >> >> > > amavisd-new does not use spamd, it uses the Mail::SpamAssassin Perl > module. Typically there is no reason to start up spamd. It's idle > because it's not doing anything. > Have you enabled the ram disk for amavis temporary files? That made a huge difference on my system. For my system I have the following in /etc/rc.d : amavisd_ram="100M" For my 1gb system with 2 amavis processes, seems to do the trick for me with no swapping. As I recall, amavis processing dropped from about 40s to 3-4s on my lowly dual P3-300 system. Gerry
------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ AMaViS-user mailing list AMaViS-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
