Stress Test 2012-03-05

From Kolmisoft Wiki
Revision as of 18:13, 14 March 2012 by Mindaugas (talk | contribs)
Jump to navigationJump to search

Results

Transcoding G729-G711 Media Pass-through Short Calls (Random 0-300s) Reached calls
Icon check.png Icon check.png Icon check.png ~250
Icon cross.png Icon check.png Icon check.png ~500
Icon cross.png Icon cross.png Icon check.png ~1000
Icon cross.png Icon cross.png Icon cross.png 4599



Conclusions

  • RAM is not important sending calls. Maximum usage 2.5 Gb was reached but mainly due to GUI usage (Active Calls and some stats pages)
  • CPU is very important - the faster, the better
  • SSD disc RAID1 really helped a lot in high CPS sessions
  • MySQL service took < 10% at peak times and is not important
  • Asterisk service takes major CPU power and is main bottleneck in the long run
  • Voice quality degrades at the time of high CPS (high HDD usage)
  • 20 CPS reached without problems, if more - Asterisk chokes



Used hardware

3 equal servers:

CPU: Intel Core i5-2400 (4 Cores)
HDD: 2x 120 GB SSD (RAID1)
RAM: 16 GB DDR3
LAN: 100 Mbps



Setup

Origination server -> Measured Server -> Termination server

One call was always life for testers to hear audio (MOH), to notice when quality degrades.

Calls were originated using script which generates call files in batches (5-10-20-50-100).

Destination was random in a format XXXXXXXXXX, where X in [0..9]



Screenshots

Transcoding, Media Pass-through, Short Calls (~250 calls)



No Transcoding, Media Pass-through, Short Calls (~500 calls)



No Transcoding, Direct Media, Short Calls (~1000 calls)



No Transcoding, Direct Media, Long Calls (Random 300-3000s) (peak 4599 calls)




See also: