I've been trying out sipXecs and as is common these days I've been doing so in a variety of virtual environments:
1. VMware ESX 3.5 and vSphere 4 2. VMware Workstation 3. KVM 4. OpenVZ (container "virtualization") on CentOS or Proxmox (Debian 5) My question is: Does this *really* need this much memory to get working or am I just not fully aware of what I am seeing? In every instance, I see really, really strange memory usage numbers. It seems that no matter how much memory I allocate to the VM (or container), as soon as "service sipxecs start" begins doing its thing, memory use jumps to almost 100%! Right now, I am using VMware Workstation running Proxmox (Debian 5) with an OpenVZ container (CentOS 5.2 w/ sipXecs) running. My memory use looks like this: Host: Windows 7 vmware-vmx.exe process shows 920mb of memory consumed. SipXecs STARTED: Proxmox VM shows 761mb of memory consumed OpenVZ container shows 2.5gb of memory used! (basically everything allocated to it) SipXecs STOPPED: Proxmox VM shows only 450mb memory consumed OpenVZ container shows 40mb in use I've tried upping the memory allocation to 4GB -- as soon as sipXecs starts (or something in it), memory use again goes to 100%. What am I doing wrong here? Thanks! _______________________________________________ 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/
