From: Mark M. <Mar...@ij...> - 2011-02-17 19:55:08
|
Peter, > I have just implementetd a new mailsetup based on postfix 2.7.0 > amavisd-new 2.6 and spamassassin 3.3.1 on ununtu 10.04 LTS > > Somehow scanning is just to slow. I have the following in the logfiles ( > loglevel=2): > > Feb 17 20:20:13 mxgw1.sdu.dk amavis[12250]: (12250-08) TIMING-SA > total 80160 ms - parse: 3 (0.0%), extract_message_metadata: 29 (0.0%), > get_uri_detail_list: 15 (0.0%), tests_pri_-1000: 6 (0.0%), tests_pri_-950: > 1.32 (0.0%), tests_pri_-900: 1.42 (0.0%), tests_pri_-400: 76554 (95.5%), > check_bayes: 76545 (95.5%), tests_pri_0: 3541 (4.4%), check_dkim_adsp: 166 > (0.2%), check_spf: 650 (0.8%), poll_dns_idle: 644 (0.8%), check_dcc: 238 > (0.3%), check_razor2: 1813 (2.3%), check_pyzor: 72 (0.1%), tests_pri_500: > 5 (0.0%), get_report: 1.96 (0.0%) > > and in here the test_pri which I don't know what is is consuming a > resaonably amount of time. The entries in TIMING-SA may overlap, so the sum of them typically exceeds the total. As in the above case: the tests_pri_-400 (76 seconds) includes the bayes test check_bayes (76 s). So, the bayes test accounts for all but 4 seconds in your case. The tests_pri_-400 can be disregarded. > The overall is between 20 and 150 seconds is this is simply to much. > > What can I do to solve this problem ? Are you having bayes data on a file-based database? This is a certain performance killer with large databases, even more with auto-expiry enabled. Switch bayes to SQL. See README and schemas in the sql/ subdirectory of the SpamAssassin package. If using MySQL, use the Mail::SpamAssassin::BayesStore::MySQL as a bayes_store_module, along with an InnoDB engine! Mark |