You really only need a couple of minutes of debug log to check
shut down declude.
rename the decmmdd.log
change to log level debug for 5 minutes.
start declude
run for a couple of minutes
shut down declude
change log level to normal
start declude
A couple of other ideas.
Virus scanner are CPU hogs. Run the virus scanner after junkmail. AVAFTERJM
I believe.
Run Message Sniffer? Run it in Persisent mode? Put in the new update for
better performance. Use weightgate to not run on every message.
Checking and IP4r blacklists that are dead?
Use SKIPIFWEIGHT and/or STOPONFIRSTHIT (?) in your filters.
----- Original Message -----
From: "Chris Anton" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, October 31, 2006 3:32 PM
Subject: [Declude.JunkMail] How long is each test taking?
Hello... We are using declude 2.somethign... we are pegged at 100%
processor usage and are wondering what is the best way to determine how
long each test takes. I am nervous to change the log level because we
handle 100k per day. Please advise. Thanks!
-Chris
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
