On Fri, 2010-05-21 at 15:37 -0400, Bowie Bailey wrote:
> Jean-Paul Natola wrote:
> > I am constantly getting the server reached --max children setting
> > entries in my log
> >
> > I started with 10 max children and have been raising it by 2. I am
> > now at 40 , but still getting the messages (though not as often) how
> > high can I go given these specs:
> >
> > sa 3.3 on freebsd , hardware is a PIV 1.3 ghz with 1 gig of ram
Lower than 40. Your RAM can't handle it.
> > 20 gig 5400 rpm PATA drive, and processing an average of 8000
> > messages a day.
Ahem. So every mail can take 10 seconds, and you would need only a
single child for that...
Your problem definitely is *not* lack of yet more SA children.
> > When running top I have seen swap usage go as high as ~500M
>
> Lower it until you see the swap usage go away. Having messages waiting
> for an available child is MUCH better than having the system using swap.
Any chance mail is piling up galore at times, maybe even as a result of
going into swap? Appears to me throttling of the MTA isn't working as it
should, and instead loves to hammer SA with all requests at once.
I definitely agree with Bowie. Avoid swap.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
