Load Test Results - XR3000

Date

23.February.2010

Notes

1. Astribank drivers were compiled with an enabled OPTIMIZE_CHANMUTE parameter. As a result, Astribank drivers do not send voice packets for DAHDI performance (echo cancellation, etc.) for channels with no active calls. This option is applied for FXS/FXO channels. The E1/T1 channels are not affected.
2. The Astribank xpp driver was configured for delegation of most work on hardware interrupts to so-called 'tasklets' (parameter rx_tasklet of xpp.ko module).
3. The Flash Operator Panel server was not active.
4. Asterisk was running without the real time priority.
5. All FXS extensions were configured for immediate start. The Asterisk extensions context was defined as follows:
   [music-test]
   exten => s,1,Answer()
   exten => s,2,Playback(music-8khz-10min)
   exten => s,3,Goto(2)
   The calls were initiated by analog telephone simulators.
6. For VoIP call tests an additional PCI Ethernet board EN-9230TX-32 (Realtek-based) was used instead of the motherboard's Ethernet interface.
7. Codec used: Open source codec_g729-ast14-gcc4-glibc-pentium4.so
8. I/O ports on Xorcom's FXS (analog-only) models, which support the activation of peripheral devices such as door locks and alarms, do take their toll on the system, and as such are noted here.
9. To be included in the number of maximum simultaneous calls, the voice in the call had to be clear, without interruptions.
10. Important Note: The tests below were not performed for applications such as call centers, conference bridges and predictive dialers. These and other processing-intense applications DO require the more robust processor!!!

Recent Webinar Discusses These Results; Provides Asterisk Server Optimization Tips

In a Webinar held recently, the results of the load tests were discussed. Xorcom technical staff provided several tips for optimizing performance in Asterisk-based servers, relating to a variety of topics including hardware component selection and Asterisk tuning. The recorded version of the Webinar is available for download from the Xorcom Web site in various formats, under the name “Five Culprits that Kill Asterisk IP-PBX Performance”.

Test #1: XR3000 with 20 XR0008 devices (32 FXS ports each) connected.

Test #2: XR3000 with 4 XR0056 devices (4 E1/T1 ports each) connected and G.729 SIP calls.

Test #3: XR3000 with 4 XR0056 devices (4 E1/T1 ports each) connected and G.711a SIP calls.

Test #4: XR3000 SIP calls (G.729 → G.711).

Note: We tested for a maximum of 500 concurrent calls. Therefore, the actual upper limit is unknown.

 Download this document as a PDF file (385.11 Kb)