Kami, I'm running ten IP4r tests, referred to in my original email as an "external DB query." There seems to be a descrepency between this as a cause and Scott's answer:
> the Declude process should not show high CPU usage in this case. > Declude uses the "Sleep()" command, which gives up CPU cycles to > other programs (and will prevent the Task Manager from showing CPU > usage in Declude during idle times, such as when Declude JunkMail is > waiting for an external or DNS-based test to complete). Assuming we're all talking about the same thing, Declude continues to run as a process waiting for replies from IP4r requests but does not consume much CPU time while doing so. Does pulling out IP4r tests during an episode show a immidiate decline in CPU use? Does anyone know how the people hosting the IP4r tests feel about us slamming them with queries? Suppose I'm cruising along with 20,000 queries a day, then jump to 500,000 over a few weeks, surely that makes an impression somewhere? Is there a point were we should ask about doing more? Thanks Dan On Wednesday, June 4, 2003 1:33, Kami Razvan <[EMAIL PROTECTED]> wrote: >Hi Dan: > >We had a similar problem. I posted a couple of messages regarding this very >issue. We were having CPU at 100% for minutes.. & in one case when a mail >list hit our server with a lot of users receiving the message at the same >time the CPU was at 100% for almost an hour. We could not do anything... >Finally the Declude processes disappeared and all was back to >normal again. > >What I noticed was the cause more than anything else was the IP4r tests. >Declude appears to be fast in filtering and everything that it does. The >IP4r tests are a different story and naturally out of Declude hands. We had >a lot of them and by taking them off it brought things to >normal. > >I stated this in an earlier posting- we are not doing all of our IP4r tests >in IMail version 8. It works much faster and since it caches it seems like >it works great. We have about 60 IP4r tests (majority of what is listed in >Declude/junkmail/manual.htm site. We will take some off and add others as >we find their effectiveness but for now we are using a lot of them and no >problem. > >I am interested to see if this helps you if you try it. > >Regards, >Kami > >-----Original Message----- >From: [EMAIL PROTECTED] >[mailto:[EMAIL PROTECTED] On Behalf Of Dan Patnode >Sent: Tuesday, June 03, 2003 9:36 PM >To: [EMAIL PROTECTED] >Subject: [Declude.JunkMail] Declude Processes & Server Load > > >We added about 350 users to our 2000+ user dual server configuration in the >last week and were doing pretty well until this afternoon. Suddenly the CPU >load graph stopped looking like its normal Donky Kong video game simulation >(up and down) and more resembled a 100% highway with a few dips. Declude >processes were taking quite a while to clear before finishing, to be >replaced by another. I pulled out some multi thousand line tests and it >nary made a dent. > >Just before bringing our 3rd server into the fold, things quieted down. >While I've already ordered 2 new dual processor 1U's, I want to par down (if >not eliminate) the variables invovled: > >1) If an external DB query slowed things down, delaying each Declude >process, would Declude still show high CPU consumption while waiting and >would the graph still be pegged? If not, is there any situation external to >my server that would? > >2) Is it possible for Declude to be consuming CPU cycles while idling for >some other reason? > >3) If something else is running in the background, eating cyles, does >Declude 'look' like its working harder? > >4) If a user (or users) all received masses of attached files (say multi >megabyte), would this slow things down in the way described? > >5) When a new client reports having 30 users, whats the best way to decipher >if this is the case? Is there a log analyzer that inventories unique >addresses (understanding that 1 user can have many addresses). > > >Thanks! >Dan > >--- >[This E-mail was scanned for viruses by Declude Virus >(http://www.declude.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 was scanned for viruses by Declude Virus >(http://www.declude.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 was scanned for viruses by Declude Virus (http://www.declude.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.
