At 04:41 PM 12/29/2006, Bob Pierce wrote: >I'm just looking at our scan times from our amavis scanners and >wondering if there might be some way to bring the average scan time >down. > >We're currently averaging about 6 seconds per message on our scanners. >We're scanning about 600,000 messages per day > >We're using: >ClamAV >Spamassassin >-DCC (local DCC server) >-Razor2 >-FuzzyOCR >-rbl checks (local rpldnsd and local bind cache) > >Is there any way to track how long each portion of the scan takes for a >message? It would be handy to know for each message how long the virus >scan took, how long the rbl checks take, how long FuzzyOCR takes... etc.
Log level 2 (in amavisd.conf) will give a breakdown of the times. Very likely 90% or more is spent in spamassassin, >On a side note, we aren't running SpamAssassin as spamd. It had been my >understanding that Amavisd-new was recommended to not run with spamd. Is >that still the case? Are there any performance improvements with running >it in either configuration? amavisd-new pre-loads the spamassassin modules directly, there is no advantage to using spamd (in fact not possible to use spamd without restructuring amavisd-new). -- Noel Jones ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
