Len Conrad wrote: >>> But I still feel there's something throttling amavis with the current >>> hardware. This machine groans on passing 900 - 1100 msgs/hour? I >>> think it can do a lot better.
You need to find out where the bottleneck is. Most "average" email messages should go through amavisd-new in a few seconds with ~95% of the time spent in SA. Running amavisd-nanny for a couple minutes will show if you are really using all your amavis workers. Running amavisd-new at loglevel 2 or above will log timing details. I expect this to tell you that amavisd-new is spending all its time running spamassassin, but best to confirm this before barking up the wrong tree. Then you can run amavisd with sa-debug or run some standalone spamassassin -D scans from the command line to see where SA is spending its time. The usual suspects are RBL or other network tests. Maybe temporarily disable those tests (or set their timeouts really low) in SA. Other things that commonly take a long time are a slow file system or using a non-deamonized virus scanner, such as using "clamscan" rather than "clamdscan". Remember - measure twice, cut once. -- Noel Jones ------------------------------------------------------------------------- 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/
