Matt,
Yeah -- I'd never use less than 1GB.
But here's the thing that I feel might have given you the wrong idea
about what I am doing:
Host Container
Physical 256 2048
Swap 1792 0
OpenVZ does not give the container any swap space. It can't do that
because it's not a hypervisor, you're not giving it dedicated disk.
So, as far as the CentOS container is concerned, it has 2GB of RAM and
no swap space.
I do not mind if OpenVZ swaps out most of the
unused-yet-mysteriously-allocated-by-java because this is not a high
disk-IO application.
FYI: The "host" is a Debian 5 x64 system, the "container" is CentOS 5.2
i386 running sipXecs 4.0.4. You should give OpenVZ a look. I've got many
years of VMware ESX experience in very large environments, but OpenVZ is
scoring points quickly for me.
-- Robert
Matt White wrote:
I'd be careful running sipx with anything less than 1GB. We have
never had success with anything less than 1GB....even with a small 5
user environment. After a while service like voicemail will slow
until they don't respond.
Like other have noted, sipx is memory hungry. If your looking for
multi-tenant, we have had "fair" success with VMWare ESX and it's
ability to memory share between VM's which helps a fair amount.
-M
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
