https://issues.apache.org/SpamAssassin/show_bug.cgi?id=6633

--- Comment #13 from Marcin <b...@mejor.pl> 2011-09-21 15:10:56 UTC ---
AXB: I think exim acl doesn't bring any new idea because i can reproduce this
problem using spamc. Imho problem is: why spamd idles and doesn't return any
response to client?
Mark: Now i can see problem isn't with bayes (btw, here is timing with bayes:
timing:
total 112630 ms - init: 12826 (11.4%), parse: 586 (0.5%),
extract_message_metadata: 23647 (21.0%), get_uri_detail_list: 2087 
(1.9%), tests_pri_-1000: 66 (0.1%), compile_gen: 1178 (1.0%), compile_eval: 112
(0.1%), tests_pri_-950: 49 (0.0%), tests_pri_-900: 54 (0.0%), tests_pri_-400:
15186 (1
3.5%), check_bayes: 15111 (13.4%), tests_pri_0: 41549 (36.9%), tests_pri_500:
515 (0.5%)

and without bayes:
timing: total 101894 ms - init: 10177 (10.0%), parse: 478 (0.5%),
extract_message_metadata: 24270 (23.8%), get_uri_detail_list: 2280 (2.2%),
tests_pri_-1000: 66 (0.1%), compile_gen: 1288 (1.3%), compile_eval: 94 (0.1%),
tests_pri_-950: 51 (0.0%), tests_pri_-900: 52 (0.1%), tests_pri_-400: 47
(0.0%), tests_pri_0: 48233 (47.3%), tests_pri_500: 445 (0.4%)

both was invoked with such command: spamassassin -t -D timing -x -L <test.email
). It looks bayes isn't bootleneck.

Next chapter, i've run strace, tcpdump. It's going to be very interesting.
Spamd sends: 
SPAMD/1.1 0 EX_OK
Spam: False ; 1.9 / 5.5
but client doesn't receive response (client is on the same host and i'm
stracing spamc). This is strange for me. It's happened only for specific emails
(probably for those one scanned very long). 

My summary: bayes performance isn't problem in my case. The root problem is
"dying" tcp connection beetwen spamc and spamd. I'll try to investigate this.
(I have no such problem when spamc connects to spamd using socket).
I think bug should be closed with something like "wontfix".

-- 
Configure bugmail: 
https://issues.apache.org/SpamAssassin/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

Reply via email to