On 2013-03-28 12:10, Richard Stupek wrote:
Ok looking at the log I see quite a few messages taking over a second
to process (samples below):
s u='20130328155503' m=\temp\1332407477322.msg' s='0' r='0'
p s='1172' t='1109' l='72697' d='127'/
g o='0' i='12.130.136.172' t='u' c='0.486243'
Richard,
Do you have any directories with a large number of files (4k)? We had a
similar problem a few months back with sniffer scans taking much longer to
complete and sniffer temporary files being left over. We finally traced the
performance issues to a frequently accessed directory with
Answer: pretty darn fast for a system that I think is slow anyway
I think my MTA is a busy system, and I know that it's not MessageSniffer
that keeps the server busy. A glance with Task Manager or Process
Explorer shows very little CPU time is spent by MessageSniffer.
I threw some grepping
Nice stats, Andrew!
And Pete, thanks for spending so much time and effort to make it work so
well, despite us beating on you because it doesn’t catch every spam campaign
from the very first message! Sniffer has always been our number one tool in
this battle.
Darin.
From: Colbeck, Andrew
