Dale,
In a subsequent email to the group, I found that the vast, vast majority
of resources are tied up in Java. Also, due to a strange configuration
in Sun's default jvm.cfg, java tried to allocate an absurd amount of
memory if the server has 2gb or more RAM.
OpenVZ is a container-based, not
On Sat, 2009-11-21 at 06:56 -0600, Robert B wrote:
> My situation is that I am attempting to overcome the non-existence of
> "true" multi-tenant support (not meant as an insult) via running
> multiple sipXecs PBXs inside of OpenVZ containers. I was drawn to
> sipXecs over Asterisk for a variety
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:
HostContainer
Physical256 2048
Swap17920
OpenVZ does not give the container any swap space. It can't do that
because it's n
I'd be careful running sipx with anything less than 1GB. We have never had
success with anything less than 1GBeven 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
m
Tony,
My point is that OpenVZ containers will not show *any* swap space
available or in use, because there isn't any. There can't be because
containers don't work like that. If this were a KVM or VMware virtual
machine (something powered by a hypervisor of sorts), obviously there's
be a swap p
984.8426
Fax: 434.984.8427
Helpdesk Contract Customers:
http://www.myitdepartment.net/gethelp/
- Original Message -
From: Robert B
To: Tony Graziano
Cc: sipx-users@list.sipfoundry.org
Sent: Sat Nov 21 12:07:42 2009
Subject: Re: [sipx-users] Question regarding resource usage...
Tony,
Tony,
Okay -- working theory here. The thing in my environment which is
"different" is that I am using OpenVZ.
I started running into issues with *fresh* installs immediately failing
on service start-up. All kinds of Java JVM memory allocation errors.
First of all, with Sun's java is execut
The voicemail/media server aspect can be very heavy from a resources
standpoint. Work is ongoing in 4.1 to replace the current voicemail system
(will then utilize freeswitch), which should provide lighter resource usage
"I think".
On Sat, Nov 21, 2009 at 7:56 AM, Robert B wrote:
> Tony,
>
> Than
Tony,
Thanks for the reply!
I guess what concerns me is that the memory allocation, in my case, is
instantaneous. It doesn't take a day or two, more like a *second* or two. :)
My situation is that I am attempting to overcome the non-existence of
"true" multi-tenant support (not meant as an ins
To a certain extent, within a few hours or days, it is not at all unusual
for sipx to assume use of 100% of your available RAM and keep it there. I
remember asking this ages ago and got a great explanation from Dale, but I
can't easily find that message.
I think it caused so many unnecessary quest
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
11 matches
Mail list logo
