Jump to: navigation, search

Resource Manager and MRCP Proxy Capacity Testing

Table: Resource Manager and MRCP Proxy Capacity Testing describes the capacity testing for overall system performance when the Resource Manager and MRCP Proxy (Windows only) are tested with multiple MCP instances.

Table: Resource Manager and MRCP Proxy Capacity Testing
Application Type Hardware Peak CAPS Peak Ports Comments
Resource Manager (Windows)
SIP Call

(Resource Manager performance)

2x Core 2 Quad Xeon x5355, 2.66 GHz 800 Any number Using both TCP and UDP.
Results occur regardless of the port density or the type of calls routed.
Multiple MCP instances are required to achieve the peak CAPS.
Reporting Server configured in one of two ways:
  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
    If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call

(Resource Manager performance with 1000 tenants configured.)

2x Core 2 Quad Xeon x5335, 2.66 GHz 600 Any number Results occur regardless of the port density and the type of calls being routed. To achieve the peak CAPS, multiple Media Control Platforms might be required.

Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
    If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled.
SIP Call

(Resource Manager performance with MSML embedded in SIP INFO messages.)

2x Core 2 Quad Xeon x5335, 2.66 GHz 300 Any number To achieve the peak CAPS, multiple Media Control Platforms might be required.

Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call

(Resource Manager performance)

4 Virtual Cores, Intel Xeon E5-2695, 2.40 GHz 800 Any number Tested on TLS only.

Results occur regardless of the port density or the type of calls routed.
Multiple MCP instances are required to achieve the peak CAPS.
Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call

(Resource Manager with Active - Active HA Pair performance)

4 Virtual Cores, Intel Xeon E5-2695, 2.40 GHz 500+500=1000 Any number Tested on UDP only.

Results occur regardless of the port density or the type of calls routed.
Multiple MCP instances are required to achieve the peak CAPS.
Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call

(Resource Manager with Active - Active HA Pair performance)

4 Virtual Cores, Intel Xeon E5-2695, 2.40 GHz 400+400=800 Any number Tested on TCP only.

Results occur regardless of the port density or the type of calls routed.
Multiple MCP instances are required to achieve the peak CAPS.
Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
Resource Manager (Linux)
SIP Call

(Resource Manager performance)

2x Core 2 Quad Xeon x5355, 2.66 GHz 800 Any number Using both TCP and UDP. Results occur regardless of the port density or the type of calls routed. Multiple Media Control Platform instances are required to achieve the peak CAPS.


Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call

(Resource Manager performance)

2x Core 2 Quad Xeon x5355, 2.66 GHz 600 Any number In this scenario, 100K of DID numbers are configured and mapped to 262 IVR applications, and defined without wild cards or ranges.
In other words, ordinary one-to-one mappings.
Results occur regardless of the port density or the type of calls routed.
Multiple Media Control Platforms required to achieve the peak CAPS.
Reporting Server configured in one of two ways:
  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call

(Resource Manager performance)

2x Core 2 Quad Xeon x5355, 2.66 GHz 800 Any number In this scenario, 1 million DID numbers are configured and mapped to 262 IVR applications, and defined in a multi-tenant environment (32 tenants with 30~35K of DIDs per tenant), without wildcards or ranges—In other words, simple one-to-one mappings.
Results occurs regardless of the port density or the type of calls routed.
Multiple Media Control Platforms required to achieve the peak CAPS.

Reporting Server disabled
(due to the fact that the Reporting Server is unable to support 1 million DIDs).

SIP Call

(Resource Manager performance with MSML embedded in SIP INFO messages.)

2x Core 2 Quad Xeon x5355, 2.66 GHz 350 Any number Multiple Media Control Platforms required to achieve the peak CAPS.

Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call
(Resource Manager performance)
2x Core 2 Quad Xeon 5355, 2.66 GHz 200 Any number Tested on UDP only on RHEL 6.4 x64. GVP 8.1.7 or later.

Results occur regardless of the port density or the type of calls routed.
Multiple MCPs are required to achieve the peak CAPS.
Reporting Server Configured in one of two ways:

  • Enabled, but No-DB mode—Without the DB (all data dropped), Reporting Server can afford much higher capacity.
  • Disabled
    With Reporting Server and DB enabled the peak CAPS bottleneck will be due to RS (see below).
SIP Call
(Resource Manager performance)
4 Virtual Cores, Intel Xeon E5-2695, 2.40 GHz 800 Any number Tested on TLS only. Results occur regardless of the port density or the type of calls routed. Multiple MCP instances are required to achieve the peak CAPS.


Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and the DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
SIP Call
(Resource Manager with Active - Active HA Pair performance)
4 Virtual Cores, Intel Xeon E5-2695, 2.40 GHz 400+400=800 Any number Using both TCP and UDP.

Results occur regardless of the port density or the type of calls routed. Multiple MCP instances are required to achieve the peak CAPS. Reporting Server configured in one of two ways:

  • Enabled and in No-DB mode—Without the DB (all data is dropped), the Reporting Server can handle much higher capacities.
If both Reporting Server and DB are enabled, a peak CAPS bottleneck would occur. See SIP Call (Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server) in Table: Reporting Server Capacity Testing.
  • Disabled
MRCP Proxy (Windows)
MRCPv1 requests(MRCP Proxy performance) 2x Core 2 Quad Xeon x5355, 2.66 GHz 1600 N/A Tested with simulated MRCP servers and clients; calculation is based on MRCP sessions. Tested on Windows 2008 R2.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on 11 July 2018, at 01:47.