Difference between revisions of "Softswitch performance"

From Kolmisoft Wiki
Jump to navigationJump to search
Line 26: Line 26:
* Calls length (big capacity of short calls (e.g. Call Center traffic) take much more system resources comparing with long calls)
* Calls length (big capacity of short calls (e.g. Call Center traffic) take much more system resources comparing with long calls)


To get an idea how many concurrent calls MOR can handle, please check [[Performance tests | results of stress tests]].
<br>
<br>
<br>
<br>

Revision as of 10:38, 4 July 2014

Single server performance

Performance results in the following conditions (SIP protocol, no transcoding, CPS is low (<5), other processes than calls are not in use) are:

  • MOR - 500 concurrent calls with media, 4000 concurrent calls (only signalling)
  • M2 - 1000 concurrent calls with media, 8000 concurrent calls (only signalling)



Multi-server performance

If you need better performance than single server solution can offer, you should use multi-server implementations.



Factors which determine call performance

Call capacity vary depending on the following factors:

  • Hardware specifications
  • Components running on same server (splitting database and GUI on different server increases performance a lot)
  • GUI usage (to generate invoices, reports, etc)
  • Additional functionality usage (recordings, IVRs, transcoding, etc)
  • Calls length (big capacity of short calls (e.g. Call Center traffic) take much more system resources comparing with long calls)



See also