On 03/30/2011 09:40 AM, Fred Christian wrote:
Thanks for the ideas,
Yes, the VPS is on OpenVZ - no swap. currently 256mb RAM with 384mb
burstable.
Sounds like I should up it to 512mb (768 burstable)
If it would be helping? I wouldn't mind helping with the wiki and
putting in a short section somewhere that mentions typical memory
requirements. Maybe it could go in the FAQ near discussion of
dependencies.
Fred
Also keep an eye on the limits you have set for the container. It's not
just about the memory. Once your virtual container is running, check the
beancounters on the host for your VEID - cat /proc/user_beancounters
and change the limits if you see any failcnt.
http://wiki.openvz.org/UBC_secondary_parameters
On Tue, Mar 29, 2011 at 8:48 PM, Bharath Chari
<[email protected] <mailto:[email protected]>> wrote:
On 03/30/2011 08:05 AM, Eric Shubert wrote:
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?
I think bumping up memory to 512 MB should be good enough for the
load you anticipate. That's what I use for a low load server such
as what you outline. Regarding swap - which virtualization
software are you using? If it's openvz, there's no swap :)
Bharath
