Opps, I noticed I said "using 75% of ram" I meant to say 75% of cpu. On
the ram side I do have to restart decludeproc on a weekly basis
otherwise its virtual memory usage creeps the process to the 2GB mark
collapsing itself.
For my systems running invURIBL and Sniffer with the volume we deal with
our system would be crippled with 1Gb of memory.
In general as long as your not experiencing backup's than your
configuration is working fine for you.
Darrell
----------------------------------
Check out http://www.invariantsystems.com for utilities for Declude,
Imail, mxGuard, and ORF. IMail/Declude Overflow Queue Monitoring,
SURBL/URI integration, MRTG Integration, and Log Parsers.
David Dodell wrote:
On Feb 10, 2008, at 1:42 PM, Darrell ([EMAIL PROTECTED]) wrote:
David,
It really depends on several factors: how you have Declude configured
(tests, filters, etc), how many threads your running, volume.
It's not uncommon to see for me to see decludeproc on a dual proc xeon
2.4ghz using 75% of ram, but I am running ~50 threads at a volume of
200K+ messages per day.
Thanks Cliff ... I'm running a ton of tests, including INVURL and
SNIFFER ... so maybe I'm not doing so bad
---
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.
