> 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.
We had this problem because vscan was inefficiently unzipping archives to scan the files inside. But our symptoms included iowait times. ------------------------------------------------------------------------- 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/
