Hey Matt,
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!)
Should we do some testing with Asterisk 13?
--
KB
On Tuesday, September 9, 2014 at 5:01 PM, Matthew Jordan wrote:
On Tue, Sep 9, 2014 at 5:01 PM, Krandon <krandon.bruse@xxxxxxxxx> wrote:The problem seems to be with only some of the audio files we are converting with SOX. I'm sure that's where the issue is. Sorry for the alarm!Phew.There were some major performance improvements with media that went into 13, so if you were running that, I'd be more suspicious. The media core in 12 is the same as 11, so there shouldn't be much difference in that version.Just to give an update - we've currently had a single Asterisk box (quad core 3.0ghz - 8 gigs of ram - SSD) handle over 150 concurrent ARI calls with playback - originating about 10 new call requests per second.That's awesome news. If you don't mind me asking, what's the load on the box with that call rate?
--Matthew JordanDigium, Inc. | Engineering Manager445 Jan Davis Drive NW - Huntsville, AL 35806 - USACheck us out at: http://digium.com & http://asterisk.org_______________________________________________asterisk-app-dev mailing list
_______________________________________________ asterisk-app-dev mailing list asterisk-app-dev@xxxxxxxxxxxxxxxx http://lists.digium.com/cgi-bin/mailman/listinfo/asterisk-app-dev
