RE: [Declude.JunkMail] Declude using 50% cpu

[Kami Razvan]

Title: Message

Hi;

 

Let me share our experience and what we did to help it.

 

1:  We put all the IP4r tests in IMail (of course version 8 if you have it)

2:  Created a weight XHeader file and gave the header that appears for each test a weight.  The following is a snapshot of what we have for the file:

 

HEADERS          8          CONTAINS          X-IMAIL-SPAM-DNSBL: (BHOLE-RUSSIA
HEADERS          5          CONTAINS          X-IMAIL-SPAM-DNSBL: (BHOLE-YIPES
HEADERS          1          CONTAINS          X-IMAIL-SPAM-DNSBL: (BLARS
HEADERS          1          CONTAINS          X-IMAIL-SPAM-DNSBL: (COMPU
HEADERS          1          CONTAINS          X-IMAIL-SPAM-DNSBL: (DELINK
HEADERS          6          CONTAINS          X-IMAIL-SPAM-DNSBL: (DSBL
HEADERS          1          CONTAINS          X-IMAIL-SPAM-DNSBL: (DSBLALL

 

3:  With IMail version we also moved the kill list to IMail from Declude.  In previous versions IMail did not handle Kill lists very well but with 8 and the wild card we changed our kill list and moved to IMail.  This helped a lot since emails are simply blocked at IMail level and never make it to Declude.  This reduced a lot of load since Declude will never see an email from a blacklisted address.  We know that Declude finishes everything it has to before taking the action, delete in this case, so if Declude will delete the message anyway why let it see it to start with?

 

Of course these may not matter much to most but we have a lot of filter files so perhaps our imposed load is a tad out of ordinary.

 

All these together - simply taking the best of both worlds - eased the load on the server.

 

I am sure others have other experiences but this is our experience.

 

Regards,

Kami

 

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Gordon
Sent: Thursday, July 24, 2003 4:05 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [Declude.JunkMail] Declude using 50% cpu

Thanks for that info Andrew, however I am looking at the task manager for my box and even 1 declude process was taking 50% then it popped up another process with 45% granted these go away when the messages are finished, however this server passes a LOT of traffic, so the number of processes for imail is default (30), I hope it wouldnt use that many for it would kill the box. I let declude run for 2 hours and my monitors reported 95-100% cpu usage consistantly.

-----Original Message-----
From: Colbeck, Andrew [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 3:56 PM
To: '[EMAIL PROTECTED]'
Subject: RE: [Declude.JunkMail] Declude using 50% cpu

Mark, it may be interesting for you to note that we don't set the number of instances of Declude directly.  Instead, the "max processes" limit in your IMail SMTP advanced settings is what governs the total number of IMail and declude.exe instances.

 

Also, an important infrastructure detail is that IMail calls one declude.exe for each message (not recipient), and declude.exe quits after it is done. Watch Task Manager for a while, sort alphabetically, and watch the number of declude.exe instances come and note that their PIDs are always changing.

 

When I first evaluated Declude JunkMail Pro, I had assumed it ran as a service and IMail passed it data as necessary.  This was entirely wrong, so the previous two paragraphs would have been helpful to me.  I hope they help you.

 

Andrew 8)

-----Original Message-----
From: Mark Gordon [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 24, 2003 12:15 PM
To: '[EMAIL PROTECTED]'
Subject: [Declude.JunkMail] Declude using 50% cpu

We are evaluating declude and have noticed a considerable increase in the cpu cycles associated with mail delivery. Is there anyway have it run in an isolated cpu instance? since there are multiple instances of declude.exe running, I would guess it would be hard to lock it down.