Storage System Performance Specifications

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
 
(18 intermediate revisions not shown)
Line 1: Line 1:
'''Go to: [[Before You Buy or Deploy - Considerations for Design and Procurement]]'''<br>  
'''Go to: [[Before You Buy or Deploy - Considerations for Design and Procurement]]'''<br>  
-
<br>
+
This content has moved to a new page: [[UC Virtualization Storage System Design Requirements]]
-
 
+
-
This page illustrates IOPS under various conditions for Unified Communications applications. This area is under construction. Check back frequently for updates.
+
-
 
+
-
== 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| 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  ===
+
-
 
+
-
{| border="1" style="text-align: center; width: 75%;"
+
-
|-
+
-
! 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.
+
-
 
+
-
<br>
+
-
 
+
-
== Cisco Unified Attendant Consoles  ==
+
-
 
+
-
This section provides the IOPS data for Cisco Unified Attendant Consoles (using Enterprise Attendant Console to produce heaviest load). Load test and average operations are represented. These tests use the published OVA&nbsp;template for Cisco Unified Attendant Consoles.
+
-
 
+
-
{| width="1172" height="253" cellspacing="1" cellpadding="1" border="1" style=""
+
-
|-
+
-
| valign="middle" bgcolor="#cccccc" align="center" colspan="9" | '''LOAD TESTING'''
+
-
|-
+
-
| <br>
+
-
| valign="middle" align="center" colspan="3" | '''IOPS (Read)'''
+
-
| <br>
+
-
| valign="middle" align="center" colspan="3" | '''IOPS (Write)'''
+
-
| <br>
+
-
|-
+
-
| <br>
+
-
| valign="middle" align="center" | '''Min'''
+
-
| valign="middle" align="center" | '''Max'''
+
-
| valign="middle" align="center" | '''Average'''
+
-
| <br>
+
-
| valign="middle" align="center" | '''Min'''
+
-
| valign="middle" align="center" | '''Max'''
+
-
| valign="middle" align="center" | '''Average'''
+
-
| '''Operating Conditions'''
+
-
|-
+
-
| Cisco Unified Attendant Console Server
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 1013.605
+
-
| valign="middle" align="center" | 0.442
+
-
| <br>
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 1112.87
+
-
| valign="middle" align="center" | 12.121
+
-
| 5,000 calls per hour, 25 concurrent operators, continuous LDAP&nbsp;sync, full logging
+
-
|-
+
-
| Upgrade
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 320.006
+
-
| valign="middle" align="center" | 3.691
+
-
| <br>
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 105.001
+
-
| valign="middle" align="center" | 10.341
+
-
| Major upgrade
+
-
|-
+
-
| valign="middle" bgcolor="#cccccc" align="center" colspan="9" | '''AVERAGE OPERATIONS'''
+
-
|-
+
-
| <br>
+
-
| valign="middle" align="center" colspan="3" | '''IOPS (Read)'''
+
-
| <br>
+
-
| valign="middle" align="center" colspan="3" | '''IOPS (Write)'''
+
-
| <br>
+
-
|-
+
-
| <br>
+
-
| valign="middle" align="center" | '''Min'''
+
-
| valign="middle" align="center" | '''Max'''
+
-
| valign="middle" align="center" | '''Average'''
+
-
| <br>
+
-
| valign="middle" align="center" | '''Min'''
+
-
| valign="middle" align="center" | '''Max'''
+
-
| valign="middle" align="center" | '''Average'''
+
-
| '''Operating Conditions'''
+
-
|-
+
-
| Cisco Unified Attendant Console Server
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 11.6
+
-
| valign="middle" align="center" | 0.092
+
-
| <br>
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 561.05
+
-
| valign="middle" align="center" | 10.82
+
-
| Synchronized directory, cached BLF, minimum online changes
+
-
|-
+
-
| Upgrade
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 107.001
+
-
| valign="middle" align="center" | 5.751
+
-
| <br>
+
-
| valign="middle" align="center" | 0
+
-
| valign="middle" align="center" | 50
+
-
| valign="middle" align="center" | 3.57
+
-
| Minor upgrade
+
-
|}
+
-
 
+
-
<br>
+
-
 
+
-
<br>
+
-
 
+
-
== Contact Center  ==
+
-
 
+
-
=== [[Virtualization for Unified CCE|Contact Center Enterprise]]<br>  ===
+
-
 
+
-
The SAN must be able to handle the following Unified CCE application disk I/O characteristics.
+
-
 
+
-
<br>
+
-
 
+
-
{| class="wikitable FCK__ShowTableBorders"
+
-
|-
+
-
! rowspan="2" | Unified CCE Component
+
-
! colspan="3" | IOPS
+
-
! colspan="3" | Disk Read KBytes / sec
+
-
! colspan="3" | Disk Write KBytes / sec
+
-
! rowspan="2" | Operating Conditions
+
-
|-
+
-
| '''Peak'''
+
-
| '''Avg.'''
+
-
| '''95th Pct.'''
+
-
| '''Peak'''
+
-
| '''Avg.'''
+
-
| '''95th Pct.'''
+
-
| '''Peak'''
+
-
| '''Avg.'''
+
-
| '''95th Pct.'''
+
-
<br>
+
-
 
+
-
|-
+
-
| Router
+
-
| 20
+
-
| 8
+
-
| 10
+
-
| 520
+
-
| 30
+
-
| 180
+
-
| 400
+
-
| 60
+
-
| 150
+
-
| rowspan="3" | 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
+
-
<br>
+
-
 
+
-
|-
+
-
| 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
+
-
|}
+
-
 
+
-
<br>
+
-
 
+
-
=== [[Virtualization for Unified CCX|Contact Center Express/IPIVR IOPS]]  ===
+
-
 
+
-
The following table lists the IOPS numbers for Unified Contact Center Express/IPIVR.
+
-
 
+
-
{| border="1"
+
-
|-
+
-
! IOPS Type
+
-
! 2vCPU
+
-
|-
+
-
| IOPS Avg per VM
+
-
| 150
+
-
|-
+
-
| IOPS Max spike per VM
+
-
| 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>
+
-
 
+
-
----
+
{| border="1" class="wikitable"
{| border="1" class="wikitable"
|-
|-
-
! style="background-color: rgb(255, 215, 0);" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
+
! style="background-color: rgb(255,215,0)" | '''Back to:''' [[Unified Communications in a Virtualized Environment|Unified Communications in a Virtualized Environment]]
|}
|}

Latest revision as of 02:24, 31 July 2012

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

This content has moved to a new page: UC Virtualization Storage System Design Requirements

Back to: Unified Communications in a Virtualized Environment

Rating: 1.0/5 (1 vote cast)

Personal tools