-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Barker
Sent: Tuesday, October 25, 2005 4:14 PM
To: [email protected]
Subject: RE: [Declude.JunkMail] 30511 problem
Andy, don't be scared I can hold you hand :)
>> How do I explain the apparent inconsistency where users
report that
>> the
CPU consumption is considerable higher than in the prior version?
First we need to confirm that it is decludeproc that has
increased in CPU usage. So far I have not seen any real
statistics for this other than what has been posted on the
boards. But I am certainly trying to validate this information.
>> How can the various "process" settings make any difference
- at worst
>> it
should spike quickly and then be idle?
Why do you think it should spike and then become idle ?
>> What is spending all this other CPU time on? Looping, looking for
directory content?
Perhaps an incorrect assumption, Declude actually uses less
CPU, between 3% and 20% on average.
David B
www.declude.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Andy Schmidt
Sent: Tuesday, October 25, 2005 2:33 PM
To: [email protected]
Subject: RE: [Declude.JunkMail] 30511 problem
Okay, I'm watching these discussions - as I'm still truly
scared of upgrading Declude.
I just can't figure out the logic behind all the CPU
consumption and why certain process parameters are suspected
to have detrimental effects.
Please verify my thinking:
A machine that needs to process a given amount of mail will
require a certain number of instructions, which are reflected
in the total CPU usage.
If several messages come in almost simultaneously, then I can
either process them right away using parallel processes,
causing a short spike in CPU use - or I can process them one
by one, using up the same CPU time over time and causing a
few seconds delay in mail delivery.
Either way, the overall CPU consumption should be the same -
just distributed differently.
So - if the above is true, how do I explain the apparent
inconsistency where users report that the CPU consumption is
considerable higher than in the prior version? How can the
various "process" settings make any difference - at worst it
should spike quickly and then be idle?
If the old Declude handled the amount of mail with moderate
CPU use and without causing noticeable delays in mail
delivery to the users - then I can't see how the same outcome
suddenly should require x times the CPU resources, no matter
how inefficient the process settings are? What is spending
all this other CPU time on? Looping, looking for directory content?
Best Regards
Andy Schmidt
Phone: +1 201 934-3414 x20 (Business)
Fax: +1 201 934-9206
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
GlobalWeb.net Webmaster
Sent: Tuesday, October 25, 2005 10:13 AM
To: [email protected]
Subject: RE: [Declude.JunkMail] 30511 problem
I changed the THREADS to 75 and CPU wnet down to about avg
50%. I'll try
WAITFORMAIL in just a bit.
I also noticed in my spool folder I have a new folder called
"s" that appeared with the time stamp of the new proc
install. There is nothing in it; just a blank folder. I deleted it.
Sincerely,
Randy Armbrecht
Global Web Solutions, Inc.
804-346-5300 x112
877-800-GLOBAL (4562) x112
http://globalweb.net
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Barker
Sent: Tuesday, October 25, 2005 9:39 AM
To: [email protected]
Subject: RE: [Declude.JunkMail] 30511 problem
Randy try changing
WAITFORMAIL 1500
To
WAITFORMAIL 500
See if that changes the delay.
David B
www.declude.com
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
GlobalWeb.net Webmaster
Sent: Monday, October 24, 2005 7:16 PM
To: [email protected]
Subject: RE: [Declude.JunkMail] 30511 problem
We upgraded to 3.0.5.11 tonight - big difference in CPU in
that it's way down from the 3.0.5.5 - but proc folder will
accumulate approx 35-50 messages before it'll dump them to
the work folder. Do not see any problems so far except for
the second or two delay in this...
We have in our declude.cfg:
THREADS 50
WAITFORMAIL 1500
WAITFORTHREADS 1000
WAITBETWEENTHREADS 1
Sincerely,
Randy Armbrecht
Global Web Solutions, Inc.
804-346-5300 x112
877-800-GLOBAL (4562) x112
http://globalweb.net
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of
Harry Vanderzand
Sent: Monday, October 24, 2005 1:52 PM
To: [email protected]
Cc: 'Technical Support'
Subject: RE: [Declude.JunkMail] 30511 problem
Dual Xeon 3.4Ghz 2GB ram imail 8.05 declude, sniffer & invurbl
The issue is that without changing anything other than going
to 3.05.11 this occurs
It appears that processing has changed
If I could get some idea from Declude about this.
Maybe I have to change my declude.cfg?
It currently is
threads 20
waitformail 500
waitforthreads 1500
waitbetweenthreads 100
Harry Vanderzand
inTown Internet & Computer Services
11 Belmont Ave. W., Kitchener, ON,N2M 1L2
519-741-1222
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of John Carter
> Sent: Monday, October 24, 2005 1:30 PM
> To: [email protected]
> Subject: RE: [Declude.JunkMail] 30511 problem
>
> Interesting ... .11 is working for me better than any
previous version
> -- proc and work are quickly cleared.
>
> What process is jumping the CPU up so high? Decludeproc or the
> anti-virus
> scanner(s) or something else? How about some more info (CPU, RAM,
> declude.cfg contents, do you run AVAFTERJM?, that kind of thing.)
>
> John
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Harry
> Vanderzand
> Sent: Monday, October 24, 2005 12:10 PM
> To: [email protected]
> Subject: [Declude.JunkMail] 30511 problem
>
> When I switch from 3.05.9 to 3.05.11 CPU usage goes up considerably
> and mail gets processed much slower and starts to backlog.
>
> I have had to switch back to 3.05.9
>
> Harry Vanderzand
> inTown Internet & Computer Services
> 11 Belmont Ave. W., Kitchener, ON,N2M 1L2
> 519-741-1222
>
>
> ---
> 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.
>
>
---
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.
---
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.
---
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.
