Ok. Here are the graph details of SpamAssassin performance:
<<inline: spam_clean-day.png>>
spam_clean_day: (5 min avg)
Max spam: 1304.0 msgs Average spam: 489.0 msgs Current spam: 516.0 msgs
Max clean: 7224.0 msgs Average clean: 1309.0 msgs Current clean: 1357.0 msgs
<<inline: spam_clean-week.png>>
spam_clean_week: (30 min avg)
Max spam: 2064.0 msgs Average spam: 534.0 msgs Current spam: 479.0 msgs
Max clean: 8415.0 msgs Average clean: 1248.0 msgs Current clean: 2977.0 msgs
Thanks again, ~Jerome Cartagena
On Feb 25, 2005, at 10:35 AM, Matt Kettler wrote:
At 01:28 PM 2/25/2005, Jerome Cartagena wrote:I am using spamassassin through MailScanner on a University mail server to help perform spam checks. I am using:
SpamAssassin version 3.0.2
running on Perl version
I have setup some scripts (spam-stats) to generate MRTG stats to help give us an idea of how well performance is going. My main problem/question is that according to our statistics we are reaching some sort of upper bound on spam scanning performance.
I don't get it, as the graph axises are completely unlabeled...
