<HTML><BODY>
Hi,<BR>
<BR>
We have been evaluating building some custom software on top of Asterisk <BR>
12, interacting via the new REST interface.<BR>
<BR>
Since this will likely be a fairly high-throughput system, part of our <BR>
evaluations involved a simple continuous loop performing GET requests to <BR>
various endpoints in order to determine ARI's reactions to a constant <BR>
stream of requests.<BR>
<BR>
While ARI does indeed perform admirably, we did note that Asterisk's <BR>
memory usage climbs throughout the test run, and the memory used is <BR>
never released. Essentially, if left long enough, it will consume all <BR>
available memory on a system.<BR>
<BR>
We've tested on two different installs, using the latest SVN checkouts <BR>
of the Asterisk 12 branch (this issue seems persistent across all the <BR>
builds we've done, so I doubt it's something introduced via any new ARI <BR>
features in the latest commits). It's otherwise completely standard <BR>
configuration-wise, with only ARI and AMI enabled.<BR>
<BR>
The issue can be easily duplicated via a simple Javascript loop <BR>
performing any sort of GET request. I can provide the script we used if <BR>
required.<BR>
<BR>
What we're interested in finding out at the moment is, is this a known <BR>
issue (nothing like this on the issue tracker at the moment), and is <BR>
this perhaps considered an "acceptable" leak at the moment, considering <BR>
the apparent slow speed at which it allocates memory (although it seems <BR>
related to the size of the GET response - getting a list of existing <BR>
bridges does it faster than an empty list of bridges), or do you suppose <BR>
have we configured something wrong or not enabled something during our <BR>
builds which might be causing this.<BR>
<BR>
<BR>
Unfortunately we do not really have the C skills in-house to track down <BR>
or determine if/where the problems lie.<BR>
<BR>
<BR>
Regards,<BR>
<BR>
- Ken<BR>
<br /><br />
<p style="font-family: Verdana; font-size:10pt; color:#666666;">
Disclaimer and Confidentiality Note:
This e-mail communication, its attachments, if any, and any rights attaching to it are, unless the context clearly indicates otherwise, the property of Nashua Communications. It is confidential, private and intended for the addressee only. If you are not the intended recipient and receive this communication in error, you are hereby notified that any review, copying, use, discloser or distribution in any manner whatsoever is strictly prohibited. Please notify the sender immediately that you have received this e-mail in error and delete the e-mail and any copies of it. Views and opinions expressed in this e-mail are those of the sender unless clearly stated as those of Nashua Communications. Nashua Communications accepts no liability for any loss or damage whatsoever, and howsoever incurred or suffered resulting or arising from the use of this e-mail communication and/or its attachments.
Nashua Communications does not warrant the integrity of this e-mail communication nor that it is free of errors, viruses, interception or interference.
Nashua Communications, its divisions and subsidiary companies expressly excludes sections 11, 12, and 13 of the Electronic Communications and Transactions Act, 25 of 2002 (“the ECT”) in respect of e-contracting. No data message or electronic communication will be recognised as having a legal contractual status under the ECT Act. All agreements concluded by Nashua Communications will only be legally binding when reduced to physical writing and physically signed by a duly authorised representative of Nashua Communications.
For more information about Nashua Communications, visit our website at www.nashuacommunications.co.za
</p></BODY></HTML>