Hello, I've got several postfix/amavis filtering types of installs setup. On my most recent one, I've hit a snag that I haven't yet been able to figure out. This particular server handles about 70k messages per day, which is generally fine. Anyhow, things will churn along fine for days and then all of a sudden I'll get a backlog in my active postfix queue (meaning things are still churning, but it can't process messages as quickly as it's getting them in).
Looking at the TIMING log entries that amavisd-new creates, I get things like this: update_cache: 17135 (67%) So, 17 seconds for the "update_cache" step. Can anyone elaborate on what exactly that is? /var/amavis is currently on a ramdisk, (freebsd 6.0) so it shouldn't be disk IO related. Also, is this related to the $enable_global_cache setting? If so, what exactly does this cache do? Thanks, --falz ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ 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/
