2009/9/18 Karsten Bräckelmann <guent...@rudersport.de>:
> On Sat, 2009-09-19 at 09:48 +1200, Jason Haar wrote:
>> On 09/19/2009 09:13 AM, Jose Luis Marin Perez wrote:
>> > For more than 10000 emails a day how much memory should be the server?
>> > as one can calculate the amount of memory needed?
>>
>> 10,000 a day means you are running a "real" mail server (ie not just for
>> your home), as such you really need a "real" server. I'm surprised
>
> The CPU should be capable of handling it, I guess. I mean, I've set up
> more than a single SA server on an Atom CPU, each of them pretty much
> bored to death -- granted, not 10k messages a day each, but still,
> they're just idling...
>
> The RAM is the killer here. With half a Gig, I'd feel uncomfortable
> running SA for 10k messages a day. And then there's ClamAV, the MTA, and
> probably more. I just hope he's not also running...
>
> Crap. I was about to say something along the lines of "webserver,
> mediawiki and thus SQL server", but -- he is!
>
> This reminded me of the fact that he is running an SQL server for user
> prefs, AWL and Bayes. Wow.
>
>
> This machine NEEDS more RAM. In fact, I'd guess half of the spam
> slipping through is due to timeouts. Thrashing into hell.
>
throwing ram at a server is not a solution in this case. 512MB is
sufficient to handle this mail load, as indicated by his post showing
little swap utilization on the system and confirmed by my real world
experience. here we handle over 1 million messages per day per node,
each node has 1GB ram. ram required is easily calculated by base
services + SA instance usage X number of instances you'd like to use.
having less instances generally just means slight (very slight in most
cases) delays. having more instances than your ram can contain means
big delays. properly configured server will not start swapping and
falling over when a flood of mail comes in, mail simply spends more
time in queue. the difference between 1 second and 1 minute in queue
is not usually significant to users.
the problem here is bad administration. hopefully with the advice
given on list and better yet some time spent studying docs, this can
be corrected.
>
>> you're not swapping to hell. What does the system "feel" like? What does
>> top say? What does the spamd syslogs say? I'd think you'd be having all
>> sorts of issues - which would impact how well spamd operates.
>>
>> BTW, my questions are rhetorical. I mean you need to do "SysAdmin-y"
>> type things to ensure the solution you have in place is operating
>> correctly - there is no "one answer" that anyone can give you that works
>> for everyone. Read man pages, etc.
>
> --
> 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; }}}
>
>
