< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index  

Re: [reSIProcate-users] Question about reSIProcate memory usage


Lyon,

You need to let all call finishes, and wait a little bit time to let all timers expires, and then see if memory goes back to the value when repro starts.

If you want to check memory leak, run repro with a small CPS, for example 5 or 10 CPS under valgrind, and then let all call finishes, wait a little bit time, then clean shutdown repro, you will see the memory leak.

Another way is to use google performance tool (http://goog-perftools.sourceforge.net/) to check the memory leak if you do not want to clean shutdown the repro. Google performance tool also does not degrade the performance of repro under high CPS load.

/Kaiduan


From: "liang.liang12@xxxxxxxxxx" <liang.liang12@xxxxxxxxxx>
To: "resiprocate-users@xxxxxxxxxxxxxxx" <resiprocate-users@xxxxxxxxxxxxxxx>
Sent: Fri, November 26, 2010 4:50:27 AM
Subject: [reSIProcate-users] Question about reSIProcate memory usage


Hi, All

Currently I meet one problem with reSIProcate for memory issue: I setup reSIProcate and run "repro" as one SIP proxy. At the same time, I run two sipp(http://sipp.sourceforge.net/) instances as UAC and UAS on the same server with simple 2-way call scenario. I observed that no matter how many the CPS(Call Per Second) is, the number of memory used by repro is increasing.... The memory increase speed increases along with high CPS number. So if I run some high CPS, my 4GB memory will be exhausted soonly.......

I don't think it's reasonable, so want to turn you whether this is one issue or there is some walk-around/solution or this is what current reSIProcate does......

For reSIProcate version, I'm using release 1.6.

If any log needed, pls. let me know. Thanks a lot for your help!

Thanks,
Lyon
--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error plea se notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.