-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 9 Jun 2002, Derrick Hudson uttered the following:
>| >| Yeah the spam[c/d] setup. My average is around 15 seconds, well it >| >| is an old p133 the slowest appears to be 93 seconds. I am a dialup >| >| user and when I go online off peak for the first time, fetchmail >| >| can throw over a 1000 emails at spam[c/d]. I also use DCC and have >| >| no performance problems there. >| > >| > The real problem you have is not so much spamd's performance, but >| > the fact that it sits idle 99% of the time, then gets slammed with >| > 1K messages in a matter of seconds. Even with my Duron 750 and not >| > much else happening, the box can effectively freeze (no UI >| > response) with a load average of 30 if I hit it with 900+ messages >| > almost instantaneously. >| >| This is very true, 99% of the time spamd sits there waiting for >| something to happen and then suddenly the poop hits the fan and >| everything goes haywire. >| >| But if I disable spamc in Exim (I used your example config) and leave >| dcc only I never get above a load average of 2.3 and dccd is flooding >| with remote servers as well, pointing out that I use spamd with -L. > > spamd is CPU bound. dcc is I/O (network) bound. You won't see a > system load from processes that are blocked on I/O. This is above me so I will accept what you say :) >| > What you should do is >| > 1) put this in your exim.conf (IIRC you're using exim) >| > deliver_queue_load_max = 5.0 2) At least while you're >| > retrieving your mail, run queue runners quite often. I >| > think the debian default is every 15 minutes. >| > >| > What this will do is cause exim to only queue the messages, no >| > delivery processing (SA scanning), if the system's load average is >| > above 5. When the load average drops below the threshold, the next >| > queue runner will attempt a delivery. By doing this you can spread >| > the load over a larger amount of time and not feel the effects as >| > much. >| > >| > Eg my system is "always on", so mail arrives as it arrives (usually >| > one at a time) so SA has no difficulty snagging a bit of CPU for a >| > couple seconds even while I'm doing all sorts of other work on the >| > machine. >| >| I have your setup in place and using the router with a domains option >| to restrict to to a couple of domains that I collect and forward to >| another remote box, one of these averages around 5 emails per >| collection and spamd will bring BSOD over the load average of 5. > > Adjust the deliver_queue_load_max to suit. I have brought it down a little bit and will see what happens. >| Strange thing is that I have a couple of those dyn dns entries and >| somethings I will get 3 or 4 spam mails at once, these also hit >| performance. but the real problem is that I need something better >| than a p133 to host spamd :) > > Sure, for a CPU bound process the best thing you can do is give it > more CPU (or reduce the process' need for CPU). > > See what happens if you add the load limiting options into your exim > config, but pick a reasonable load for your system. Choose a value > that will let spamd process stuff as soon as is reasonable, but that > also won't kill your system. I have currently got the mail box at 3.5 with a queue delivery of 10 minutes, this I am increasing to 20 minutes as it hits inbounds anyway. Sometimes it can take me upto 30 minutes just to bring the first batch of mail in. > Another alternative, if you aren't collecting mail all that often, is > to just let it hit the roof and take a coffee break :-). That's what > I had to do that time I fed 900+ messages into exim (without that > option set) and could no longer get any UI response at all. After the > dust settled I saw a load average of 30, but who knows what it was > before that. There was no harm done that time. Now, I do have > another box that I've pulled all mail handling from (it didn't even > have SA on it) because with only 8MB RAM it would thrash too much and > the kernel would start killing processes. On that system no mail > handling is appropriate. > My Mailbox has 24 mb on it but it also handles the nntp server as well although that is moving this week to another box. My scripts from the main box connect to the net, start the dcc flood (so that my stuff is upto date), brings in nntp, does some fidonet net work, then calls a tcpip port on the mailbox to start fetchmail to bring in the mail, nothing else will occur until the mail is brought in. What I may try is to do a normal batch run at 6pm without mail collect, then let that drop and then get the system to reconnect 10 minutes later and do a mail run. Sean - -- Sean Rima http://www.tcob1.net Linux User: 231986 Jabber: [EMAIL PROTECTED] THE VIEWS EXPRESSED HERE ARE NOT NECESSARILY THOSE OF MY WIFE. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Use GPG for Secure Mail iD8DBQE9BJfmeR/L2ZZp3E8RAvnaAJ4h0vlwS8jfO4XznT4tJfRd/XXRQACgtTpG t29VHiubP+HAc3eN+MWpG88= =AKqC -----END PGP SIGNATURE----- _______________________________________________________________ Don't miss the 2002 Sprint PCS Application Developer's Conference August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
