Difference between revisions of "Softswitch performance"
| Line 8: | Line 8: | ||
Performance of [[Implementations | multi-server solution]] in ideal conditions (no extensive GUI usage and no transcoding): | Performance of [[Implementations | multi-server solution]] in ideal conditions (no extensive GUI usage and no transcoding): | ||
* MOR - up to 2000 concurrent calls | * MOR - up to 2000 concurrent calls, up to 100 CPS | ||
* M2 - up to | * M2 - up to 10 000 concurrent calls, up to 1000 CPS | ||
<br> | <br> | ||
== Factors that influence softswitch performance == | == Factors that influence softswitch performance == | ||
Revision as of 08:08, 27 April 2020
Performance of single server solution in ideal conditions (no extensive GUI usage and no transcoding):
- MOR - up to 500 concurrent calls, up to 25 CPS (calls per second)
- M2 - up to 1000 concurrent calls, up to 100 CPS
For higher performance it is recommended to deploy a multi-server solution.
Performance of multi-server solution in ideal conditions (no extensive GUI usage and no transcoding):
- MOR - up to 2000 concurrent calls, up to 100 CPS
- M2 - 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?
Real examples
In all of below examples companies are 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.
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.
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.
