Jump to: navigation, search

Reporting Server Capacity Testing

This section describes the capacity of overall system performance when the Reporting Server is tested with multiple Media Control Platform instances.

The tables in this section show the performance of other GVP components individually.

  • Use these tables to determine if you encountered any performance limits beyond those already defined in other tables.
  • Use these tables if you are interested in determining the overall system limits, which may occur in VoiceXML, media services, reporting, RM, or other functions.
Table: Reporting Server Capacity Testing
Application Type Hardware Peak CAPS Peak Ports Comments
SIP Call

Reporting Server in partitioning mode with Microsoft SQL 2008 Enterprise Server

Reporting Server:
2x Core 2 Quad Xeon x5355, 2.66 GHz

Microsoft SQL Server DB:
2x Core 2 Quad Xeon x5355, 2.66 GHz

270 Any number
32,400 (~30,000 based on a 120 seconds call duration)

Results occur regardless of the port density or the type of calls processed.
Resource Manager and Media Control Platform log information to the Reporting Server using default settings. Increased reporting and logging can reduce Reporting Server capacity.
Microsoft SQL database is installed on Windows 2008 Server with the database files residing on a 15k rpm HDD Disk Array.

SIP Call

Reporting Server in partitioning mode with Oracle 10g R2 Server

Reporting Server:
2x Core 2 Quad Xeon x5355, 2.66 GHz

Oracle DB:
2x Core 2 Quad Xeon x5355, 2.66 GHz

270 Any number Results occur regardless of the port density or the type of calls processed.

Resource Manager and Media Control Platform log information to the Reporting Server using default settings. Increased reporting and logging can reduce Reporting Server capacity.
Oracle database is installed on Windows 2003 Server with the database files residing on a 15k rpm HDD Disk Array.

SIP Call

Reporting Server /w MS SQL Server 2008 R2 Enterprise (partitioning mode)

Reporting Server:
Quad-Core Xenon 5355 2.66GHz

MS SQL DB:
Quad-Core Xenon 5355 2.66GHz /w 15 HDD Disk Array

300 Any number Regardless of the port density and the type of calls being processed with official architecture, which RM and MCP are both logging information to RS and using default setting. Heavier reporting/logging can reduce the RS capacity.

MS SQL on Windows 2008 R2 with DB data files reside on a 15 HDD Disk Array (15k rpm)

SIP Call

Reporting Server in No DB mode

Reporting Server:
2x Core 2 Quad Xeon E5504, 2.0 GHz, 8 GB RAM
800 Any number When Reporting Server is configured in No DB mode, data that is sent to it, is dropped.

Tested with an actual Resource Manager instance (not a VM) without the Media Control Platform.

SIP Call

Reporting Server in partitioning mode with Oracle 11g Server

Reporting Server:
2x Core 2 Quad Xeon x5355, 2.66 GHz

Oracle DB:
2x Core 2 Quad Xeon x5355, 2.66 GHz /w 15 HDD Disk Array

300 Any number Results occur regardless of the port density and the type of calls being processed.

RM and MCP both log information to the Reporting Server using default settings. Increased reporting/logging can reduce RS capacity.
Oracle DB on Windows 2008 R2 x64 with DB data files that reside on a 15 HDD Disk Array (15k rpm).

Feedback

Comment on this article:

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