Return-Path: X-Original-To: apmail-spamassassin-users-archive@www.apache.org Delivered-To: apmail-spamassassin-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7C486113CE for ; Wed, 20 Aug 2014 13:15:52 +0000 (UTC) Received: (qmail 88678 invoked by uid 500); 20 Aug 2014 13:15:45 -0000 Delivered-To: apmail-spamassassin-users-archive@spamassassin.apache.org Received: (qmail 88653 invoked by uid 500); 20 Aug 2014 13:15:45 -0000 Mailing-List: contact users-help@spamassassin.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list users@spamassassin.apache.org Received: (qmail 88643 invoked by uid 99); 20 Aug 2014 13:15:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 13:15:45 +0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=SPF_NEUTRAL,URI_HEX X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted nor denied by domain of jason@redtailtechnology.com) Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 20 Aug 2014 13:15:19 +0000 Received: from [192.168.236.26] (helo=sam.nabble.com) by sam.nabble.com with esmtp (Exim 4.72) (envelope-from ) id 1XK5jS-0003oe-PS for users@spamassassin.apache.org; Wed, 20 Aug 2014 06:15:18 -0700 Date: Wed, 20 Aug 2014 06:15:18 -0700 (PDT) From: redtailjason To: users@spamassassin.apache.org Message-ID: <1408540518726-111067.post@n5.nabble.com> Subject: Delays with Check_Bayes MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello and good morning. We are running into some delays that we are trying to pin down a root cause for. Below are some examples. Within the examples, you can see that the check_bayes: scan is consuming most of the timing. Does anyone have any suggests on what to look at? We use 3.3.2. We have eight scanners setup to handle the scanning with 5GB RAM and 4 CPUs each. Volume is 250K - 500K per day. Aug 19 5:06:07 amavis[1581]: (01581-07-2) TIMING-SA total 138564 ms - parse: 2 0.00% extract_message_metadata: 37 (0.0%) get_uri_detail_list: 7 (0.0%) tests_pri_-1000: 13 (0.0%) tests_pri_-950: 1.08 (0.0%) tests_pri_-900: 1.13 (0.0%) tests_pri_-400: 137793 (99.4%) check_bayes: 137786 (99.4%) tests_pri_0: 708 (0.5%) check_dkim_adsp: 15 (0.0%) check_spf: 10 (0.0%) poll_dns_idle: 6 (0.0%) tests_pri_500: 3 (0.0%) get_report: 0.88 (0.0%) Aug 19 6:06:08 amavis[1271]: (01271-12-3) TIMING-SA total 118903 ms - parse: 1.75 0.00% extract_message_metadata: 34 (0.0%) get_uri_detail_list: 8 (0.0%) tests_pri_-1000: 7 (0.0%) tests_pri_-950: 1.11 (0.0%) tests_pri_-900: 1.18 (0.0%) tests_pri_-400: 118273 (99.5%) check_bayes: 118266 (99.5%) tests_pri_0: 419 (0.4%) check_dkim_adsp: 46 (0.0%) check_spf: 5 (0.0%) poll_dns_idle: 152 (0.1%) tests_pri_500: 156 (0.1%) get_report: 5 (0.0%) Aug 19 5:06:21 amavis[6764]: (06764-02-6) TIMING-SA total 99680 ms - parse: 2 0.00% extract_message_metadata: 37 (0.0%) get_uri_detail_list: 7 (0.0%) tests_pri_-1000: 13 (0.0%) tests_pri_-950: 1.08 (0.0%) tests_pri_-900: 1.13 (0.0%) tests_pri_-400: 98881 (99.2%) check_bayes: 98874 (99.2%) tests_pri_0: 736 (0.7%) check_dkim_adsp: 12 (0.0%) check_spf: 5 (0.0%) poll_dns_idle: 1.26 (0.0%) tests_pri_500: 3 (0.0%) get_report: 0.85 (0.0%) Aug 19 5:06:19 amavis[9621]: (09621-13-6) TIMING-SA total 99636 ms - parse: 2 0.00% extract_message_metadata: 38 (0.0%) get_uri_detail_list: 7 (0.0%) tests_pri_-1000: 12 (0.0%) tests_pri_-950: 1.09 (0.0%) tests_pri_-900: 1.14 (0.0%) tests_pri_-400: 98847 (99.2%) check_bayes: 98839 (99.2%) tests_pri_0: 726 (0.7%) check_dkim_adsp: 11 (0.0%) check_spf: 6 (0.0%) poll_dns_idle: 2 (0.0%) tests_pri_500: 3 (0.0%) get_report: 0.87 (0.0%) Aug 19 6:06:07 amavis[16447]: (16447-06-10) TIMING-SA total 90079 ms - parse: 2 0.00% extract_message_metadata: 34 (0.0%) get_uri_detail_list: 5 (0.0%) tests_pri_-1000: 9 (0.0%) tests_pri_-950: 1.24 (0.0%) tests_pri_-900: 1.35 (0.0%) tests_pri_-400: 89698 (99.6%) check_bayes: 89685 (99.6%) tests_pri_0: 323 (0.4%) check_dkim_adsp: 51 (0.1%) check_spf: 20 (0.0%) poll_dns_idle: 16 (0.0%) tests_pri_500: 3 (0.0%) get_report: 1.03 (0.0%) Aug 19 5:07:28 amavis[3901]: (03901-02-7) TIMING-SA total 87855 ms - parse: 4 0.00% extract_message_metadata: 84 (0.1%) get_uri_detail_list: 22 (0.0%) tests_pri_-1000: 32 (0.0%) tests_pri_-950: 1.10 (0.0%) tests_pri_-900: 1.18 (0.0%) tests_pri_-400: 87015 (99.0%) check_bayes: 86980 (99.0%) tests_pri_0: 699 (0.8%) check_dkim_adsp: 32 (0.0%) check_spf: 9 (0.0%) poll_dns_idle: 1.03 (0.0%) tests_pri_500: 4 (0.0%) get_report: 1.03 (0.0%) Aug 19 6:15:03 amavis[7851]: (07851-02-3) TIMING-SA total 81154 ms - parse: 2 0.00% extract_message_metadata: 41 (0.1%) get_uri_detail_list: 11 (0.0%) tests_pri_-1000: 11 (0.0%) tests_pri_-950: 1.05 (0.0%) tests_pri_-900: 1.11 (0.0%) tests_pri_-400: 80789 (99.5%) check_bayes: 80778 (99.5%) tests_pri_0: 299 (0.4%) check_spf: 6 (0.0%) poll_dns_idle: 1.31 (0.0%) tests_pri_500: 3 (0.0%) get_report: 1.14 (0.0%) -- View this message in context: http://spamassassin.1065346.n5.nabble.com/Delays-with-Check-Bayes-tp111067.html Sent from the SpamAssassin - Users mailing list archive at Nabble.com.