<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 9, 2014 at 5:16 PM, Krandon <span dir="ltr"><<a href="mailto:krandon.bruse@gmail.com" target="_blank">krandon.bruse@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>
<span style="font-size:14px">Hey Matt,</span>
</div><div><span style="font-size:14px"><br></span></div><div><span style="font-size:14px">As of right now, load is about 2.8. The majority of the problems are coming from I/O constraints first. We moved the DB off, as we had planned on doing - and also put the audio files in a ramdisk, as the same chunk of small audio files were part of every call (playback). The ARI interface is still extremely responsive. We are interested in seeing how it fails when it pushes - if the interface stays stable with a "graceful" failure, or if it effects all other calls. In the case of the manager interface, it would stop responding which immediately affected all calls. So far, we have not seen that with ARI (woohoo!)</span></div><div><span style="font-size:14px"><br></span></div><div><span style="font-size:14px">Should we do some testing with Asterisk 13?</span></div><span class="HOEnZb"><font color="#888888">
<div><div><br></div><div>-- </div><div>KB<br></div><br clear="all"></div></font></span></blockquote></div><br></div><div class="gmail_extra">That'd be great if you could. If Asterisk isn't the bottleneck then I wouldn't expect much difference, but it'd still be nice to know that the beta didn't break your scenario :-)<br></div><div class="gmail_extra"><br>-- <br><div dir="ltr"><div>Matthew Jordan<br></div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div><div>Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a></div></div>
</div></div>