We could give this a try :)

From: [email protected] 
[mailto:[email protected]] On Behalf Of Michael Picher
Sent: donderdag 5 januari 2012 13:29
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] memory leak on high load?

And does the same happen if you use DNS SRV for the Mediant?  I suppose this 
would be good to know.

Mike
On Thu, Jan 5, 2012 at 6:46 AM, Henry Dogger 
<[email protected]<mailto:[email protected]>> wrote:
Hi,

Thanks for the quick reply and to answer all of you in once :)
We are running the latest stable version of 4.4 (namely: 4.4.0- 
2011-10-12EDT17:34:54 domU-12-31-39-00-0D-21) updated with yum update after 
installation of ISO.
We are not having any DNS latency, checked this already before posting. :)
As my colleague already replied also not using any backup or other setting 
which I found in earlier cases of high memory usage.

We see a pattern as Douglas and Joegen describe it, the memory is increasing in 
a linear pattern, at a certain points some Java processes are dropping memory 
to avoid sipXproxy using swap memory, but in the end it will do this anyway....
Side note, we are connecting from a mediant via IP and not using DNS SRV, which 
should trigger the domain alias feature, not sure if this could trigger anytime 
concerning this memory issue...?
But basically the system needs a period (e.g. the night) where the load is 
lower, to recover from the high continuous load?
Again thanks for the replies :)

Kind regards,

Henry Dogger
Telecats BV

From: 
[email protected]<mailto:[email protected]>
 
[mailto:[email protected]<mailto:[email protected]>]
 On Behalf Of Joegen Baclor
Sent: donderdag 5 januari 2012 12:06
To: Discussion list for users of sipXecs software
Subject: Re: [sipx-users] memory leak on high load?

DNS latency is worth checking.  It is usually the culprit why transactions 
remain in queue for so long gradually decaying the system.

On 01/05/2012 06:42 PM, Tony Graziano wrote:
I would agree with Joegen that if the memory returns its not a leak. I think 
your question would be "why is it so slow to return". Are you testing with 4.4 
or the dev version (4.5.2)?
On Thu, Jan 5, 2012 at 5:35 AM, Elwin Formsma 
<[email protected]<mailto:[email protected]>> wrote:
Hello Tony,

We have no backup job configured. It's a pretty clean server, hardly anything 
is configured.


Regards,

Elwin Formsma
Telecats BV


Op 5 jan. 2012, om 11:27 heeft Tony Graziano het volgende geschreven:


Did you have a backup job configured and running also?
On Jan 5, 2012 4:11 AM, "Henry Dogger" 
<[email protected]<mailto:[email protected]>> wrote:
Hi all,

When testing a setup for one of our clients we came across a disturbing issue.
We generated a high load of about 180 calls per minute on the system via ISDN, 
and wanted to let this run for let's say a week.
But after one night we noticed the sipXproxy is not returning its memory or 
sipXproxy is not doing this fast enough...
When we shut the load test down, memory usage was returned back to normal in 
about an hour.
Is this normal behavior? A server under this kind of load will eventually start 
using its swap memory and then failing (we tested this).

At first we tested with a light machine (only 2Gbyte of memory), but we get the 
same results with a machine with a bigger CPU and 6 Gbyte of memory, but the 
time it takes the system to fail is longer...
Can anyone shed some light on this?
We are running: sipXecs (4.4.0- 2011-10-12EDT17:34:54 domU-12-31-39-00-0D-21)

Kind regards,

Henry Dogger
Telecats BV


_______________________________________________
sipx-users mailing list
[email protected]<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/
_______________________________________________
sipx-users mailing list
[email protected]<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/


_______________________________________________
sipx-users mailing list
[email protected]<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/



--
======================
Tony Graziano, Manager
Telephone: 434.984.8430<tel:434.984.8430>
sip: 
[email protected]<mailto:[email protected]>
Fax: 434.465.6833<tel:434.465.6833>

Email: [email protected]<mailto:[email protected]>

LAN/Telephony/Security and Control Systems Helpdesk:
Telephone: 434.984.8426<tel:434.984.8426>
sip: [email protected]<mailto:[email protected]>

Helpdesk Customers: http://myhelp.myitdepartment.net
Blog: http://blog.myitdepartment.net

Linked-In Profile:
 http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4
Ask about our Internet Fax services!



_______________________________________________

sipx-users mailing list

[email protected]<mailto:[email protected]>

List Archive: http://list.sipfoundry.org/archive/sipx-users/


_______________________________________________
sipx-users mailing list
[email protected]<mailto:[email protected]>
List Archive: http://list.sipfoundry.org/archive/sipx-users/



--
Michael Picher, Director of Technical Services
eZuce, Inc.

300 Brickstone Square

Suite 201

Andover, MA. 01810
O.978-296-1005 X2015
M.207-956-0262
@mpicher <http://twitter.com/mpicher>
www.ezuce.com<http://www.ezuce.com>

------------------------------------------------------------------------------------------------------------
Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab
A gathering for - open source users, eZuce customers & eZuce partners
Get the inside track on 4.6 and a glimpse at the future of sipXecs!

_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users/

Reply via email to