Thanks for the help guys... I figured out my problem with my
performance
issues I hope. I found my sweet spot of 7 child processes
and thanks to
Robert & this ---> spamassassin -D -t < email.txt,
I was able to watch
SA pause on an SPF check that must have gotten installed
with the "yum"
installation. I went into the init.pre and commented out
the SPF
plug-in. I also cleaned up some canned rules that I found
from Google.
I'm running FuzzyOCR and my total TIMING average around 600
- 700 ms
per. We've been running good all day and just had to tell
you guys
thanks for the help. Dirk, I will be looking into turning
on Named
locally, and turning on at least one of the network checks
back on. Not
to get off topic, but I was looking at amavis-stats, but the
site says
that its being replaced with "parser" something.
Anyways, it's still in
Beta and I don't want to really mess with any Beta stuff
right now on a
production box. Is there anything else out there that will
analyze my
amavis.log and/or Postfix and maybe even graph my TIMINGS
and throughput
(something Windows would be great, I've had enough of Linux
for awhile).
I know Maia will show spam stats, but that's not all I'm
looking for, I
want to see the boxes performance. It will be the only way
I will ever
get new hardware!
Thanks again,
Daniel
-----Original Message-----
From: Robert LeBlanc [mailto:rjl renaissoft.com]
Sent: Thursday, September 21, 2006 4:54 AM
To: Shue, Daniel G.
Cc: Maia-usersrenaissoft.com
Subject: Re: [Maia-users] Performance Issues
Shue, Daniel G. wrote:
> You can see the SA Check is the culpret. Is there
anything I can do
to
> log what SA does and get something like this so I can
see where the
> bottle neck is? Is there anything else I can do to
speed up SA?
You can get a general diagnostic by trying something like:
spamassassin -D -t < email.txt
and watching the output to see where it hangs the longest.
Start from
there before you go needlessly disabling beneficial
features.
It's also worth pointing out that depending on your hardware
and your
mail traffic load, a processing time of 6-10 seconds per
item may not be
unreasonable, particularly if you add the FuzzyOCR plugin
(which can
boost the processing times by another 2-4 seconds for items
that contain
inline images). SpamAssassin's tests are thorough, and you
can't
reasonably expect to insert a filter like this into your
mail system
without reducing your mail system's overall throughput
somewhat. You
can make SpamAssassin less thorough in its checks, of
course, to speed
things up a bit, but that rather defeats the purpose.
What you need to consider when you're thinking about adding
spam
filtering to an existing mail system is how that extra
filtering delay
is going to need to be balanced out to achieve the
throughput levels you
want. You may discover that to solve your bottleneck
problem you need
to run a second amavisd-maia box in parallel, sharing the
same Maia
database. That would put more hardware to work where it's
needed the
most, and if your mail volume calls for it you could add a
third,
fourth, fifth amavisd-maia box to the array down the road.
It's also important to realize that spam filtering is not a
job you
really want to assign to that five-year-old PII-300 that's
been
gathering dust in your basement. A lot of people make the
mistake of
thinking that they can use some old spare hardware to do the
job, but
they quickly discover that spam filtering is a very
resource-intensive
task, and their bottleneck just constricts further when the
hardware is
overloaded. Particularly now that we've entered the OCR
era, the
resource requirements of your amavisd-maia box are only
going to grow.
--
Robert LeBlanc <rjlrenaissoft.com>
Renaissoft, Inc.
Maia Mailguard <http://www.maiamail
guard.com/>
_______________________________________________
Maia-users mailing list
Maia-usersrenaissoft.com
http://www.renaissoft.com/mailman/listinfo/maia-users
|