Re: really slow spamd scan
On 10/2/06, Olivier Nicole [EMAIL PROTECTED] wrote: Are you using smapc/spamd or plain spamassassin? it is spamc/spamd.. OK, so it should be fast enough. And I think there is a way to tell spamassassin to report what tests actually take some time to execute, so you can see where you are loosing time. How can I do that? Read the manual :) I think I remember I once read something about it, but honnestly I have noanswer. Best regards, Olivier Thanks, Oliver.
Re: really slow spamd scan
Greetings, I think I have diabled the DNS and URI lookups and Razor/Pyzor/DCC, and it still takes around 1x seconds to scan one email, but we have a little power supply problem at this moment so I cannot check the configuration file, I'll check it later. I still think it may be caused by the UTF-8 locale. Since the load of that mail server is not high, so may be I just let it there for a moment if I cannot find where the problem is. Regards, Deephay
Re: really slow spamd scan
I think I have diabled the DNS and URI lookups and Razor/Pyzor/DCC, and it still takes around 1x seconds to scan one email, but we have a little power supply problem at this moment so I cannot check the configuration file, I'll check it later. Are you using smapc/spamd or plain spamassassin? And I think there is a way to tell spamassassin to report what tests actually take some time to execute, so you can see where you are loosing time. Bests, Olivier
Re: really slow spamd scan
On 9/29/06, Olivier Nicole [EMAIL PROTECTED] wrote: I think I have diabled the DNS and URI lookups and Razor/Pyzor/DCC, and it still takes around 1x seconds to scan one email, but we have a little power supply problem at this moment so I cannot check the configuration file, I'll check it later. Are you using smapc/spamd or plain spamassassin? it is spamc/spamd.. And I think there is a way to tell spamassassin to report what tests actually take some time to execute, so you can see where you are loosing time. How can I do that? thx a lot! Bests, Olivier
Re: really slow spamd scan
On Thu, 28 Sep 2006, Deephay wrote: On 9/28/06, Olivier Nicole [EMAIL PROTECTED] wrote: I am quite new to SA (a week of SA life), and the SA is working, the thing is, SA is incredibly slow on my server (2.8GHZ CPU + 2GB Memory + Qmail + Qmail-scanner). Here's a typical scan log: result: . 0 - SPF_PASS scantime=14.7,size=1689 ... Hi, Problem is not that it is slow. That SA takes 14 seconds to deliver a message is not an issue, email is not a real time process anyway and transiting email from one gateway to another can take minutes or hours. The scantime=14.7 does not mean the scan time of spamassassin? It does. 14.7 seconds to scan the message. Problem would be is SA would make high CPU load on your server. 14 seconds may be just the delay for the various network tests to respond. You mean the test form SA? Yes. The various DNS and URI blocklist lookups and Razor/Pyzor/DCC all take time to complete. A system snapshot (load average, running processes, memory consumption including swap) taken during processing of a message would help us determine whether there *is* a problem. If fifteen seconds is the high end of what you are seeing, you do not have a problem. I have googled for this kind of situations and I found I am the slowest. If I stop the spamd, the delivery will be much faster. If you are worried about a fifteen second delay in delivery of email you need to tune your users' expectations, *NOT* SpamAssassin. I've said it before and I'll say it again: Email is a best-effort, non-guaranteed store-and-forward messaging system. It is not Instant Messaging. It is not a general-purpose file transfer utility. Delays will happen. -- John Hardin KA7OHZICQ#15735746http://www.impsec.org/~jhardin/ [EMAIL PROTECTED]FALaholic #11174pgpk -a [EMAIL PROTECTED] key: 0xB8732E79 - 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79 --- Insofar as the police deter by their presence, they are very, very good. Criminals take great pains not to commit a crime in front of them. -- Jeffrey Snyder ---
Re: really slow spamd scan
John D. Hardin writes: On Thu, 28 Sep 2006, Deephay wrote: On 9/28/06, Olivier Nicole [EMAIL PROTECTED] wrote: I am quite new to SA (a week of SA life), and the SA is working, the thing is, SA is incredibly slow on my server (2.8GHZ CPU + 2GB Memory + Qmail + Qmail-scanner). Here's a typical scan log: result: . 0 - SPF_PASS scantime=14.7,size=1689 ... Hi, Problem is not that it is slow. That SA takes 14 seconds to deliver a message is not an issue, email is not a real time process anyway and transiting email from one gateway to another can take minutes or hours. The scantime=14.7 does not mean the scan time of spamassassin? It does. 14.7 seconds to scan the message. Problem would be is SA would make high CPU load on your server. 14 seconds may be just the delay for the various network tests to respond. You mean the test form SA? Yes. The various DNS and URI blocklist lookups and Razor/Pyzor/DCC all take time to complete. A system snapshot (load average, running processes, memory consumption including swap) taken during processing of a message would help us determine whether there *is* a problem. If fifteen seconds is the high end of what you are seeing, you do not have a problem. I have googled for this kind of situations and I found I am the slowest. If I stop the spamd, the delivery will be much faster. If you are worried about a fifteen second delay in delivery of email you need to tune your users' expectations, *NOT* SpamAssassin. I've said it before and I'll say it again: Email is a best-effort, non-guaranteed store-and-forward messaging system. It is not Instant Messaging. It is not a general-purpose file transfer utility. Delays will happen. In fairness, though, I would agree that 14 seconds is pretty long for most cases. On my pretty old 1.5ghz server, I get this kind of distribution: number seconds 401 0 - 1 280 1 - 2 185 2 - 3 110 3 - 4 46 4 - 5 36 5 - 6 34 6 - 7 15 7 - 8 13 8 - 9 17 9 - 10 4 10 - 11 9 11 - 12 8 12 - 13 4 13 - 14 4 14 - 15 20 15 seconds or more IOW, a large majority complete in under 4 seconds. See the wiki for speed-up tips. --j.
RE: really slow spamd scan
DNS time-outs are usually 10 seconds. 14-10 = 4, which is normal. I would check if your DNS tests run smoothly and do not time out somewhere. -Sietse From: Justin MasonSent: Thu 28-Sep-06 17:00To: John D. HardinCc: Deephay; Olivier Nicole; users@spamassassin.apache.orgSubject: Re: really slow spamd scan "John D. Hardin" writes: On Thu, 28 Sep 2006, Deephay wrote: On 9/28/06, Olivier Nicole [EMAIL PROTECTED] wrote: I am quite new to SA (a week of SA life), and the SA is working, the thing is, SA is incredibly slow on my server (2.8GHZ CPU + 2GB Memory + Qmail + Qmail-scanner). Here's a typical scan log: result: . 0 - SPF_PASS scantime=14.7,size=1689 ... Hi, Problem is not that it is slow. That SA takes 14 seconds to deliver a message is not an issue, email is not a real time process anyway and transiting email from one gateway to another can take minutes or hours. The scantime=14.7 does not mean the scan time of spamassassin? It does. 14.7 seconds to scan the message. Problem would be is SA would make high CPU load on your server. 14 seconds may be just the delay for the various network tests to respond. You mean the test form SA? Yes. The various DNS and URI blocklist lookups and Razor/Pyzor/DCC all take time to complete. A system snapshot (load average, running processes, memory consumption including swap) taken during processing of a message would help us determine whether there *is* a problem. If fifteen seconds is the high end of what you are seeing, you do not have a problem. I have googled for this kind of situations and I found I am the slowest. If I stop the spamd, the delivery will be much faster. If you are worried about a fifteen second delay in delivery of email you need to tune your users' expectations, *NOT* SpamAssassin. I've said it before and I'll say it again: Email is a best-effort, non-guaranteed store-and-forward messaging system. It is not Instant Messaging. It is not a general-purpose file transfer utility. Delays will happen. In fairness, though, I would agree that 14 seconds is pretty long for most cases. On my pretty old 1.5ghz server, I get this kind of distribution: number seconds 401 0 - 1 280 1 - 2 185 2 - 3 110 3 - 4 46 4 - 5 36 5 - 6 34 6 - 7 15 7 - 8 13 8 - 9 17 9 - 10 4 10 - 11 9 11 - 12 8 12 - 13 4 13 - 14 4 14 - 15 20 15 seconds or more IOW, a large majority complete in under 4 seconds. See the wiki for speed-up tips. --j.
really slow spamd scan
Greetings all, I am quite new to SA (a week of SA life), and the SA is working, the thing is, SA is incredibly slow on my server (2.8GHZ CPU + 2GB Memory + Qmail + Qmail-scanner). Here's a typical scan log: result: . 0 - SPF_PASS scantime=14.7,size=1689 ... . And I have checked the SA wiki and found there is a note saying if you are using UTF-8 locale, the performance can be low. What I am wondering is: Will it be that slow? Any suggestion is appreciated. Deephay
Re: really slow spamd scan
On 9/28/06, Olivier Nicole [EMAIL PROTECTED] wrote: I am quite new to SA (a week of SA life), and the SA is working, the thing is, SA is incredibly slow on my server (2.8GHZ CPU + 2GB Memory + Qmail + Qmail-scanner). Here's a typical scan log: result: . 0 - SPF_PASS scantime=14.7,size=1689 ... Hi, Problem is not that it is slow. That SA takes 14 seconds to deliver a message is not an issue, email is not a real time process anyway and transiting email from one gateway to another can take minutes or hours. The scantime=14.7 does not mean the scan time of spamassassin? Problem would be is SA would make high CPU load on your server. 14 seconds may be just the delay for the various network tests to respond. You mean the test form SA? I have googled for this kind of situations and I found I am the slowest. If I stop the spamd, the delivery will be much faster. Bests Olivier Thanks very much for the suggestion! Deephay
Re: really slow spamd scan
14 seconds may be just the delay for the various network tests to respond. You mean the test form SA? I have googled for this kind of situations and I found I am the slowest. If I stop the spamd, the delivery will be much faster. I mean it depends how your SA is configured. Some of the test are based on data on remove databases (all the RBL test, Razor/Pysor, Dcc...) depending on your network connectivity, it can take some time before you get a response for these various tests. But once again, this is not an issue because it does not create any load on your server: while SA is waiting for a network test to finish, the server can process other emails. I have an average SA processing time comprised between 10 and 15 seconds. Olivier
