Re[2]: burning cpu since 3.1
Hello Loren, That's was exactly the problem. Everything rocks great now Thanks a lot Mathieu Chateau Saturday, October 29, 2005, 8:19:21 PM, you wrote: >> Everything goes fine after spamd started. But after a while, spamd >> processes takes the whole CPU until i kill them. >> >> I removed all *.cf rules i always use to keep it fast but anyway, >> after a while, it's away. LW> If it isn't rules causing it, it must be something else. The usual cases LW> would be a bayes or awl expire run. You should check the size of these LW> databases. LW> Loren -- Best regards, Mathieumailto:[EMAIL PROTECTED]
Re: burning cpu since 3.1
> Everything goes fine after spamd started. But after a while, spamd > processes takes the whole CPU until i kill them. > > I removed all *.cf rules i always use to keep it fast but anyway, > after a while, it's away. If it isn't rules causing it, it must be something else. The usual cases would be a bayes or awl expire run. You should check the size of these databases. Loren
burning cpu since 3.1
Hello spamhunters, i upgraded two mailservers from 3.0.4 to 3.1.0. Like others on this mailing list, i am having a performance issue. platform: Spamasassin 3.1.0 (upgraded from ports) Perl 5.8.6 FreeBSD 5.4 qmail + vpopmail + qmail-scanner Both server have 1Go of Ram and two Xeon 2,4 with HTT enabled. Everything goes fine after spamd started. But after a while, spamd processes takes the whole CPU until i kill them. i got something like that: PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 14228 vpopmail 1140 28048K 26524K CPU0 0 23.5H 99.02% 99.02% perl5.8.6 14229 vpopmail 1140 26876K 25420K CPU2 2 23.3H 99.02% 99.02% perl5.8.6 I removed all *.cf rules i always use to keep it fast but anyway, after a while, it's away. in the log file: spamc[52447]: connect(AF_INET) to spamd at 127.0.0.1 failed, retrying (#1 of 3): Operation timed out Does anyone knows what's the hell is going on ? Does anyone got better performance with perl 5.8.7 ? I read somewhere that spamassassin changed the way to fork process, and know is similar to apache httpd. Is it linked ? Hope to read good news from all of you Mathieu CHATEAU
