On 03/29/2011 06:09 PM, Fred Christian wrote:
I have been reading the wiki some and I didn't find this yet. Maybe
there are too many variables.
I got some help getting a fairly basic CentOS 5.5 VPS set up with
qmailtoaster.
I ran out of RAM and had trouble even logging in with SSH
I read some list archives and got clamav shut off which was taking up
40% memory
Now in TOP I see this.
Mem: 393216k total, 219456k used, 173760k free, 0k buffers
This is without clamav taking up an additional 160mb.
Would people expect my config to take up this much RAM?
Say I have 3 users and one very active sending our 1000 emails a week,
receiving maybe 100 emails total a week.
How much RAM do you think I will need?
Is there a way to estimate the system needs?
Are there optimizations that you might recommend to clean things up?
Or am I just being cheap and should up the RAM on my VPS?
I don't expect the server to have any other significant usage, some very
basic webpages with low load.
Thanks
Fred
This is what I have presently:
Mem: 515332k total, 492312k used, 23020k free, 47192k buffers
Swap: 1044216k total, 61112k used, 983104k free, 140220k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
30658 clamav 25 0 152m 133m 7856 S 0.0 26.4 0:15.57 clamd
So clamav does take a good sized chunk.
You should reduce your /var/qmail/control/concurrencyincoming value. 3
should be ok. If you have that little mail, you should rarely go over 1.
You might get by with what you have. The only thing that's memory
intensive is scanning, both clamav and spamassassin.
What's your swap look like?
--
-Eric 'shubes'
---------------------------------------------------------------------------------
Qmailtoaster is sponsored by Vickers Consulting Group
(www.vickersconsulting.com)
Vickers Consulting Group offers Qmailtoaster support and installations.
If you need professional help with your setup, contact them today!
---------------------------------------------------------------------------------
Please visit qmailtoaster.com for the latest news, updates, and packages.
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
