Difference between revisions of "Softswitch performance"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(85 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Single server performance ==
The system performance in ideal conditions (no extensive GUI usage and no transcoding):


Performance of MOR has been [[Performance tests | tested with big traffic load]] and maximum capacity is around 500 concurrent calls per server if:
* MOR single-server solution - up to 500 concurrent calls, up to 50 CPS (most of the time it's closer to 20).
* MOR [[Implementations | multi-server solution]] - up to 2000 concurrent calls, up to 100 CPS (most of the time it's closer to 60).


* SIP protocol is used
* M4 single-server solution - up to 500 concurrent calls, up to 100 CPS
* There's no call transcoding
* M4 [[M4_System_Architecture | multi-server solution]]- up to 10 000 concurrent calls, up to 1000 CPS.
* GUI, IVR, Recordings and other extra services are not in use
* CPS (calls per second) is low (<5).  


== Multi-server performance ==
<br>
== Factors that influence softswitch performance ==  


However, if you need >500 concurrent calls, there are two options:
* [[Recommended_hardware_for_MOR_server | Hardware specifications]] (CPU, RAM, HDD type - 5400/7200 rpm, SSD, SAS, Raid, NIC etc.)
* Network (routers/switches)
* Providers (connectivity, quality, PDD)
* CPS (if you accept a lot of short calls at the same time (so called dialer or call center traffic), softswitch performance decreases)
* Structure of call (signalling only or signalling with media)
* Processes, running on the same time (if you generate invoices, statistics or run other processes, softswitch performance decreases)
* Additional functionality usage (if you record calls, use different IVR structures, softswitch performance decreases)
* Codec and protocol used
* Protocol and codec conversion (in case of transcoding performance decreases two times)
* Calls length (if you accept a lot of short calls at the same time (so called dialer or call center traffic), softswitch performance decreases)
* DB and GUI on same server or on the separate (if you separate DB and GUI, you can increase performance)
* SIP balancer present or not (if you use SIP balancer in front of the servers, you can increase performance)
* Business model (Calling Card, Callback and Call Center calls decreases softswitch performance)
* etc
<br>
See also: [http://blog.kolmisoft.com/how-do-you-select-a-softswitch-based-on-concurrent-calls/ How do you select a softswitch based on concurrent calls?]


* Use direct media (send just signalling through MOR). In this case MOR will be able to handle up to 4000 concurrent calls
<br>
* Use [[Implementations | multi-server implementations]]. In this case there are no limits of servers you can add and each core server will handle 500 concurrent calls


== Factors which determine call performance ==
== Screenshots from real use cases ==


Call capacity vary depending on the following factors:
In all of the below examples, companies were using [[Recommended_hardware_for_MOR_server | recommended hardware]].


* [[Recommended_hardware_for_MOR_server | Hardware specifications]]
=== MOR, single server solution, Wholesale Transit business ===
* Components running on same server (splitting database and GUI on different server increases performance a lot)
 
* GUI usage (to generate invoices, reports, etc)
'''Implementation''': single server with 24 cores, GUI is not used almost at all.
* 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)
'''Results''': up to 500 concurrent calls, up to 1500 call attempts per minute.
 
[[File:8.png]]
 
[[File:9.png]]
<br><br>
 
=== MOR, 4-servers solution, Wholesale Transit business === 
 
'''Implementation''': [[SIP_balancer | SIP balancer]], 3 Asterisk (MOR) servers and DB/GUI server.
 
'''Results''': 1200 concurrent calls, 1500 call attempts per minute.
 
[[File:115_Load_Stats.png]]
 
[[File:115_Load_Statsatm.png]]
<br><br>
 
 
<br><br>
 
=== M2, 7-servers solution, Wholesale Transit business ===
 
'''Implementation''': [[SIP_balancer | SIP balancer]], 5 Freeswitch (M2) servers and DB/GUI server.
 
'''Results''': 6105 concurrent calls, up to 6400 call attempts per minute.
 
[[File:6105cc.png]]
<br><br>


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


==See also==
==See also==
 
* [[CPS_Limit | CPS Limit]]
* [[Recommended_hardware_for_MOR_server | Recommended hardware]]
* [[Recommended_hardware_for_MOR_server | Recommended hardware]]
* [[Performance tests | Results of stress tests]]
* [http://blog.kolmisoft.com/how-do-you-select-a-softswitch-based-on-concurrent-calls/ How do you select a softswitch based on concurrent calls?]
* [[Performance Suggestions]]

Latest revision as of 13:37, 13 September 2024

The system performance in ideal conditions (no extensive GUI usage and no transcoding):

  • MOR single-server solution - up to 500 concurrent calls, up to 50 CPS (most of the time it's closer to 20).
  • MOR multi-server solution - up to 2000 concurrent calls, up to 100 CPS (most of the time it's closer to 60).
  • M4 single-server solution - up to 500 concurrent calls, up to 100 CPS
  • M4 multi-server solution- up to 10 000 concurrent calls, up to 1000 CPS.


Factors that influence softswitch performance

  • Hardware specifications (CPU, RAM, HDD type - 5400/7200 rpm, SSD, SAS, Raid, NIC etc.)
  • Network (routers/switches)
  • Providers (connectivity, quality, PDD)
  • CPS (if you accept a lot of short calls at the same time (so called dialer or call center traffic), softswitch performance decreases)
  • Structure of call (signalling only or signalling with media)
  • Processes, running on the same time (if you generate invoices, statistics or run other processes, softswitch performance decreases)
  • Additional functionality usage (if you record calls, use different IVR structures, softswitch performance decreases)
  • Codec and protocol used
  • Protocol and codec conversion (in case of transcoding performance decreases two times)
  • Calls length (if you accept a lot of short calls at the same time (so called dialer or call center traffic), softswitch performance decreases)
  • DB and GUI on same server or on the separate (if you separate DB and GUI, you can increase performance)
  • SIP balancer present or not (if you use SIP balancer in front of the servers, you can increase performance)
  • Business model (Calling Card, Callback and Call Center calls decreases softswitch performance)
  • etc


See also: How do you select a softswitch based on concurrent calls?


Screenshots from real use cases

In all of the below examples, companies were using recommended hardware.

MOR, single server solution, Wholesale Transit business

Implementation: single server with 24 cores, GUI is not used almost at all.

Results: up to 500 concurrent calls, up to 1500 call attempts per minute.

8.png

9.png

MOR, 4-servers solution, Wholesale Transit business

Implementation: SIP balancer, 3 Asterisk (MOR) servers and DB/GUI server.

Results: 1200 concurrent calls, 1500 call attempts per minute.

115 Load Stats.png

115 Load Statsatm.png




M2, 7-servers solution, Wholesale Transit business

Implementation: SIP balancer, 5 Freeswitch (M2) servers and DB/GUI server.

Results: 6105 concurrent calls, up to 6400 call attempts per minute.

6105cc.png


See also

Retrieved from "https://wiki.kolmisoft.com/index.php?title=Softswitch_performance&oldid=29817"