Hi Darrell, You said a key word: "spike".
That's what I've been trying to get at. Total CPU usage remains the same, it's just that tweaking these settings can allow you to spread out the CPU usage, if desired... or let it spike to process mail as quickly as possible. See my other post for a "picture"... maybe saving a thousand words <g>. Darin. ----- Original Message ----- From: "Darrell ([EMAIL PROTECTED])" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Wednesday, October 26, 2005 12:05 PM Subject: Re: [Declude.JunkMail] 30511 problem Darin, From following the thread he had his WAITFORMAIL setting set higher. Which would cause declude to wait that time once it emptied the proc directory. While declude is waiting messages are coming into the proc directory. Once declude finishes its wait time and kicks off it has a lot of messages to process. This in turn causes an influx of messages to be delivered by the queuemanager (assuming most of the messages processed are legit and make it to the spool to be processed). On my system I have seen this exact behavior. My system would process all the messages in the proc directory and kick in the waitformail setting. During this time I would get a ton of messages into the proc directory. The fix for this was to lower the waitformail time. Having seen this on my system I understand exactly why in his case queuemanger would see a higher cpu spike because it is processing messages in bursts instead of spread out. Darrell ------------------------------------------------------------------------ Check out http://www.invariantsystems.com for utilities for Declude And Imail. IMail/Declude Overflow Queue Monitoring, SURBL/URI integration, MRTG Integration, and Log Parsers. Darin Cox writes: > I don't follow. How is declude dumping more mail for QM to handle if the > load is the same? > > As Andy pointed out in another thread, total CPU instructions (usage) should > remain relatively the same under the same load. Are you perhaps seeing > peaks and valleys where you used to see an average usage in the middle? > e.g. peaks of 80-90% cpu, with valleys close to zero in between, where you > used to see 40-45% cpu steady? > > Darin. > > > ----- Original Message ----- > From: "GlobalWeb.net Webmaster" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, October 26, 2005 11:11 AM > Subject: RE: [Declude.JunkMail] 30511 problem > > > No messages slipping thru - all messgaes are being processed correctly. I'm > thnking it was just due to the waitformail in the cfg file. If declude was > waiting to process based on this, then it would be dumping a lot more mail > into the spool for QM to handle; this would cause an increase... > > Randy > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox > Sent: Wednesday, October 26, 2005 11:07 AM > To: [email protected] > Subject: Re: [Declude.JunkMail] 30511 problem > > Hmmmm... very strange. The only thing I can think of that would cause Queue > Manager to consume more CPU is if it is delivering more messages. Is it > possible that more messages are slipping through Declude with 3.0.5.11, as > compared with 3.05.5? > > Or could there be some file locking contention between IMail and Declude on > 3.05.11? > > Declude? > > Darin. > > > ----- Original Message ----- > From: "GlobalWeb.net Webmaster" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Wednesday, October 26, 2005 10:46 AM > Subject: RE: [Declude.JunkMail] 30511 problem > > > Your guess is as good as mine....but it was. And I have verified that there > is no increase in message load. > > Randy > > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox > Sent: Tuesday, October 25, 2005 4:59 PM > To: [email protected] > Subject: Re: [Declude.JunkMail] 30511 problem > > But Queuemanager is IMail, not Declude. Why would it run higher unless > there was more load on the server (i.e. more messages being processed)? > > Darin. > > > ----- Original Message ----- > From: "GlobalWeb.net Webmaster" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, October 25, 2005 4:40 PM > Subject: RE: [Declude.JunkMail] 30511 problem > > > Decludeproc runs at a higher CPU with v11 as compared to v5 - queuemgr also > runs a it higher. These 2 services are the ones that most consumes CPU with > v11 > > Randy > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Darin Cox > Sent: Tuesday, October 25, 2005 4:26 PM > To: [email protected] > Subject: Re: [Declude.JunkMail] 30511 problem > > Hmmm? You said queuemanager increased CPU usage as well. Were you just > meaning that only decludeproc and queuemanager were using CPU on the server? > > Darin. > > > ----- Original Message ----- > From: "GlobalWeb.net Webmaster" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, October 25, 2005 4:02 PM > Subject: RE: [Declude.JunkMail] 30511 problem > > > No change in message load - I randomly picked approx 7pm yesterday to > upgrade. > > Decludeproc service ran at a lower CPU at version 3.0.5.5 > > > 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 Darin Cox > Sent: Tuesday, October 25, 2005 3:53 PM > To: [email protected] > Subject: Re: [Declude.JunkMail] 30511 problem > > Hmmm... if queuemanager CPU is increasing, then that would point to more > messages being processed, wouldn't it? So it would logically follow that > decludeproc should see more CPU usage as well. > > Do you have reports to show the incoming and outgoing message load on the > server, both before and after the Declude upgrade? > > Darin. > > > ----- Original Message ----- > From: "GlobalWeb.net Webmaster" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Tuesday, October 25, 2005 3:32 PM > Subject: RE: [Declude.JunkMail] 30511 problem > > > Decludeproc and queuemgr > > Randy > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of David Barker > Sent: Tuesday, October 25, 2005 3:30 PM > To: [email protected] > Subject: RE: [Declude.JunkMail] 30511 problem > > Randy, > > Can you confirm for me the processes that are increasing the CPU ? > > David B > www.declude.com > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of GlobalWeb.net > Webmaster > Sent: Tuesday, October 25, 2005 8:46 AM > To: [email protected] > Subject: RE: [Declude.JunkMail] 30511 problem > > Allow me to make a correction - under normal daytime loads, we are seeing an > increase in CPU - steady at 80-90%. Under 3.0.5.5 we saw an average of 40% > > > 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 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. > > --- > 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. --- 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.
