Difference between revisions of "Softswitch performance"

From Kolmisoft Wiki
Jump to navigationJump to search
 
(31 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== What is the maximal single server performance? ==
The system performance in ideal conditions (no extensive GUI usage and no transcoding):


Max. performance of single server solutions ''' (real examples)''':
* 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).


* MOR - 500 concurrent calls* ([[Softswitch_performance#Wholesale_transit_business_.232 |screenshots of this business case]])
* M4 single-server solution - up to 500 concurrent calls, up to 100 CPS
* M2 - 600 concurrent calls* ([[Softswitch_performance#Wholesale_transit_business_.233 | screenshots of this business case]])
* M4 [[M4_System_Architecture | multi-server solution]]- up to 10 000 concurrent calls, up to 1000 CPS.
 
Concurrent calls limitation for single server solution:
 
* MOR - 500 concurrent calls
* M2- 1000 concurrent calls
 
Once you reach limits of a single server, it is recommended to deploy a [[Implementations | multi-server solutions]].


<br>
<br>
== What is the maximal multi-server performance? ==
* MOR - 1000 concurrent calls* ([[Softswitch_performance#Wholesale_transit_business_.231 |screenshots of this business case]])
* M2 - not tested yet (screenshots will be added soon...)
We have not implemented bigger systems than above, so it is not possible to show or predict performance results if you add more servers.
<br>
== Factors that influence softswitch performance ==  
== Factors that influence softswitch performance ==  


* [[Recommended_hardware_for_MOR_server | Hardware specifications]] (CPU, RAM, HDD type - 5400/7200 rpm, SSD, SAS, Raid, etc.)
* [[Recommended_hardware_for_MOR_server | Hardware specifications]] (CPU, RAM, HDD type - 5400/7200 rpm, SSD, SAS, Raid, NIC etc.)
* Network (routers/switches)
* Network (routers/switches)
* Providers (connectivity, quality, PDD)
* Providers (connectivity, quality, PDD)
Line 44: Line 28:


<br>
<br>
== Real examples ==
In all of below examples companies are using [[Recommended_hardware_for_MOR_server | recommended hardware]].
=== Wholesale transit business #1 === 
Implementation:
* 2 SIP balancers (in redundancy)
* 3 Asterisk (MOR) servers
* 2 DB/GUI server (with MySQL replication, redundancy)


Results: up to 1000 concurrent calls, up to 1500 call attempts per minute (25 CPS)
== Screenshots from real use cases ==


[[File:1.png]]
In all of the below examples, companies were using [[Recommended_hardware_for_MOR_server | recommended hardware]].


[[File:2.png]]
=== MOR, single server solution, Wholesale Transit business ===
<br><br>


=== Wholesale transit business #2 ===
'''Implementation''': single server with 24 cores, GUI is not used almost at all.


Implementation - single server solution (GUI is not used almost at all, server has 24 cores).
'''Results''': up to 500 concurrent calls, up to 1500 call attempts per minute.
<br>
Results: up to 500 concurrent calls, up to 1500 call attempts per minute (25 CPS)


[[File:8.png]]
[[File:8.png]]
Line 74: Line 44:
<br><br>
<br><br>


=== Wholesale transit business #3 ===  
=== MOR, 4-servers solution, Wholesale Transit business ===


Implementation - M2 single server solution with 600 concurrent calls limit.
'''Implementation''': [[SIP_balancer | SIP balancer]], 3 Asterisk (MOR) servers and DB/GUI server.
<br>
Results: up to 600 concurrent calls, > 400 call attempts per minute (>7 CPS)


[[File:15.png]]
'''Results''': 1200 concurrent calls,  1500 call attempts per minute.
<br>
[[File:16.png]]
<br><br>


=== Retail business #1 ===
[[File:115_Load_Stats.png]]


Implementation:
[[File:115_Load_Statsatm.png]]
<br><br>


* 1 Asterisk (MOR) server
* 1 DB + GUI server


Note: main business - incoming calls through DIDs
<br>
Results: up to 100 concurrent calls, up to 50 call attempts per minute (1 CPS)
[[File:10.png]]
[[File:11.png]]
<br><br>
<br><br>
=== Calling Cards and Retail business #1 ===
Implementation:


* 1 Asterisk (MOR) + DB + GUI server
=== M2, 7-servers solution, Wholesale Transit business ===


Note: main business - calling cards and retail
'''Implementation''': [[SIP_balancer | SIP balancer]], 5 Freeswitch (M2) servers and DB/GUI server.
<br>
Results: up to 100 concurrent calls, up to 800 call attempts per minute (13 CPS)


[[File:12.png]]
'''Results''': 6105 concurrent calls, up to 6400 call attempts per minute.


[[File:13.png]]
[[File:6105cc.png]]
<br><br>
<br><br>


==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 MOR stress tests]]
* [[M2_Switch_Stress_Test | Results of M2 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?]
* [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