Storage System Performance Specifications

From DocWiki

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 +
'''Go to: [[Before You Buy or Deploy - Considerations for Design and Procurement]]'''<br>
 +
 +
<br>
 +
This page illustrates IOPS under various conditions for Unified Communications applications. This area is under construction. Check back frequently for updates.  
This page illustrates IOPS under various conditions for Unified Communications applications. This area is under construction. Check back frequently for updates.  
Line 5: Line 9:
This section provides the IOPS data for a Cisco Unified Communications Manager system under load.  
This section provides the IOPS data for a Cisco Unified Communications Manager system under load.  
-
{{note| Sending CDR/CMR to the billing server does not incur any IOPS spikes, but enabling CDR Analysis and Reporting (CAR) continuous loading results in around 300 IOPS average on the system.}}
+
These values are per active VM OVA.  Which VM OVAs are active, and how many are active simultaneously, depends on how the CUCM cluster is setup (see www.cisco.com/go/ucsrnd for details).
-
As a reference, the following steady state IOPS were observed for the loads (expressed in Busy Hour Call Attempts) indicated:  
+
Active Call processing nodes: As a reference, the following steady state IOPS were observed at various loads (expressed in Busy Hour Call Attempts):  
::*10K BHCA produces ~ 35 IOPS  
::*10K BHCA produces ~ 35 IOPS  
Line 16: Line 20:
{{note| The Unified Communications Manager data is based on ~93-98% sequential writes.}}  
{{note| The Unified Communications Manager data is based on ~93-98% sequential writes.}}  
-
*Software upgrades generate 800 to 1200 IOPS in addition to steady state IOPS.  
+
*Software upgrades during business hours generate 800 to 1200 IOPS in addition to steady state IOPS.  
-
*CAR-scheduled uploads is 250 IOPS.  
+
* CDR/CMR via CDR Analysis and Reporting (CAR)
-
*Trace collection is 100 IOPS.  
+
** CUCM sending CDR/CMR to the external billing server does not incur any additional IOPS.
-
*Nightly backup is 50 IOPS.
+
** Enabling CAR continuous loading results in around 300 IOPS average on the system.
 +
** Scheduled uploads are around 250 IOPS for Publisher's VM only.  
 +
*Trace collection is 100 IOPS (occurs on all VMs for which tracing is enabled).  
 +
*Nightly backup (usually Publisher's VM only) is 50 IOPS.
== Cisco Unity Connection  ==
== Cisco Unity Connection  ==
Line 25: Line 32:
=== Summary of IOPS for Unity Connection  ===
=== Summary of IOPS for Unity Connection  ===
-
{| border="1" style="width: 75%; text-align: center;"
+
{| border="1" style="text-align: center; width: 75%;"
|-
|-
! IOPS Type  
! IOPS Type  
Line 69: Line 76:
| 413.50
| 413.50
|}
|}
 +
 +
== Unified Presence  ==
 +
 +
The CUP 1000 user OVA generates about 60 IOPS during steady-state.  Expect similar peaks as CUCM during backups and upgrades.
 +
== Contact Center  ==
== Contact Center  ==
-
=== Contact Center Enterprise<br>  ===
+
=== [[Virtualization for Unified CCE|Contact Center Enterprise]]<br>  ===
The SAN must be able to handle the following Unified CCE application disk I/O characteristics.  
The SAN must be able to handle the following Unified CCE application disk I/O characteristics.  
Line 171: Line 183:
|}
|}
-
=== Contact Center Express/IPIVR IOPS  ===
+
<br>
 +
 
 +
=== [[Virtualization for Unified CCX|Contact Center Express/IPIVR IOPS]] ===
The following table lists the IOPS numbers for Unified Contact Center Express/IPIVR.  
The following table lists the IOPS numbers for Unified Contact Center Express/IPIVR.  
Line 186: Line 200:
| 1500
| 1500
|}
|}
 +
 +
<br>
 +
 +
=== [[Virtualization for Cisco MediaSense|Cisco MediaSense]]  ===
 +
 +
The following table lists the IOPS numbers for Cisco MediaSense partitions.
 +
 +
{| cellspacing="1" cellpadding="1" border="1" style="width: 513px; height: 228px;"
 +
|-
 +
! scope="col" | Media Partitions<br>
 +
! scope="col" | IOPS Specifications<br>
 +
|-
 +
|
 +
Average IOPS for non-media partitions
 +
 +
| 1700 ops/sec
 +
|-
 +
| Average IOPS for media partitions
 +
| 50 ops/sec
 +
|-
 +
| Average bandwidth for non-media partitions
 +
| 7300 kbytes/sec
 +
|-
 +
| Average bandwidth for media partitions
 +
| 1000 kbytes/sec
 +
|}
 +
 +
<br>
 +
 +
<br>
----
----

Revision as of 19:27, 5 August 2011

Go to: Before You Buy or Deploy - Considerations for Design and Procurement


This page illustrates IOPS under various conditions for Unified Communications applications. This area is under construction. Check back frequently for updates.

Contents

Unified Communications Manager

This section provides the IOPS data for a Cisco Unified Communications Manager system under load.

These values are per active VM OVA. Which VM OVAs are active, and how many are active simultaneously, depends on how the CUCM cluster is setup (see www.cisco.com/go/ucsrnd for details).

Active Call processing nodes: As a reference, the following steady state IOPS were observed at various loads (expressed in Busy Hour Call Attempts):

  • 10K BHCA produces ~ 35 IOPS
  • 25K BHCA produces ~ 50 IOPS
  • 50K BHCA produces ~ 100 IOPS
  • 100K BHCA produces ~ 150 IOPS
Note Note: The Unified Communications Manager data is based on ~93-98% sequential writes.
  • Software upgrades during business hours generate 800 to 1200 IOPS in addition to steady state IOPS.
  • CDR/CMR via CDR Analysis and Reporting (CAR)
    • CUCM sending CDR/CMR to the external billing server does not incur any additional IOPS.
    • Enabling CAR continuous loading results in around 300 IOPS average on the system.
    • Scheduled uploads are around 250 IOPS for Publisher's VM only.
  • Trace collection is 100 IOPS (occurs on all VMs for which tracing is enabled).
  • Nightly backup (usually Publisher's VM only) is 50 IOPS.

Cisco Unity Connection

Summary of IOPS for Unity Connection

IOPS Type 1vCPU 2vCPU 4vCPU 7vCPU
Avg Total 78.66 129.01 217.89 201.73
Peak Total 760.99 714.06 867.88 773.70
Avg Read 5.90 19.60 45.67 9.53
Peak Read 601.84 469.46 693.21 526.22
Avg Write 72.77 109.40 172.22 192.20
Peak Write 247.14 293.51 371.97 413.50

Unified Presence

The CUP 1000 user OVA generates about 60 IOPS during steady-state. Expect similar peaks as CUCM during backups and upgrades.


Contact Center

Contact Center Enterprise

The SAN must be able to handle the following Unified CCE application disk I/O characteristics.


Unified CCE Component IOPS Disk Read KBytes / sec Disk Write KBytes / sec Operating Conditions
Peak Avg. 95th Pct. Peak Avg. 95th Pct. Peak Avg. 95th Pct.


Router 20 8 10 520 30 180 400 60 150 8,000 agents; 60 cps; ECC: 5 scalars @ 35 bytes each; No reporting.
Logger 1,000 600 700 4,000 600 2,500 12,000 3,000 7,000
HDS 1,600 1,000 1,100 600 70 400 6,000 2,000 3,800
Agent PG 125 40 70 300 5 20 2,000 1,200 1,500 2,000 agents, 15 cps


HDS 3,900 2,500 3,800 75,000 30,000 50,000 9,500 2,200 5,800 8,000 agents; 60 cps; 200 reporting users at max query load; ECC: 5 scalars @ 35 bytes each.
ROGGER 610 360 425 2,700 400 1,600 7,500 2,150 4,300 4,000 agents; 30 cps; ECC: 5 scalars @ 35 bytes each


Contact Center Express/IPIVR IOPS

The following table lists the IOPS numbers for Unified Contact Center Express/IPIVR.

IOPS Type 2vCPU
IOPS Avg per VM 150
IOPS Max spike per VM 1500


Cisco MediaSense

The following table lists the IOPS numbers for Cisco MediaSense partitions.

Media Partitions
IOPS Specifications

Average IOPS for non-media partitions

1700 ops/sec
Average IOPS for media partitions 50 ops/sec
Average bandwidth for non-media partitions 7300 kbytes/sec
Average bandwidth for media partitions 1000 kbytes/sec




Back to: Unified Communications in a Virtualized Environment

Rating: 1.0/5 (1 vote cast)

Personal tools