Difference between revisions of "Softswitch performance"
From Kolmisoft Wiki
Jump to navigationJump to search
| Line 2: | Line 2: | ||
* [[Recommended_hardware_for_MOR_server | Hardware specifications]] | * [[Recommended_hardware_for_MOR_server | Hardware specifications]] | ||
* Components running on same server ( | * Components running on same server (splitting database and GUI on different server increases performance a lot) | ||
* GUI usage (to generate invoices, reports, etc) | * GUI usage (to generate invoices, reports, etc) | ||
* Additional functionality usage (recordings, IVRs, transcoding, 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 | * 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]]. | To get an idea how many concurrent calls MOR can handle, please check [[Performance tests | results of stress tests]]. | ||
Revision as of 09:05, 13 May 2013
Average MOR performance is 500 concurrent calls per server and can 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)
To get an idea how many concurrent calls MOR can handle, please check results of stress tests.
