Storage System Performance Specifications

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
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>
+
<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 7: Line 7:
== Unified Communications Manager  ==
== Unified Communications Manager  ==
-
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.  These values are per active VM OVA. Which VM OVAs are active, and how many are active simultaneously, depends on how the CUCM cluster nodes are setup with respect to service activation, redundancy groups, etc. (see www.cisco.com/go/ucsrnd for details).  
-
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).  
+
CUCM storage access is on average 93-98% sequential writes with an IO block size of 4 kilobytes.
-
Active Call processing nodes: As a reference, the following steady state IOPS were observed at various loads (expressed in Busy Hour Call Attempts):  
+
*Active call processing: 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 17: Line 17:
::*50K BHCA produces ~ 100 IOPS  
::*50K BHCA produces ~ 100 IOPS  
::*100K BHCA produces ~ 150 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.  
*Software upgrades during business hours generate 800 to 1200 IOPS in addition to steady state IOPS.  
Line 24: Line 22:
**CUCM sending CDR/CMR to the external billing server does not incur any additional IOPS.  
**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.  
**Enabling CAR continuous loading results in around 300 IOPS average on the system.  
-
**Scheduled uploads are around 250 IOPS for Publisher's VM only.
+
**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).  
*Trace collection is 100 IOPS (occurs on all VMs for which tracing is enabled).  
*Nightly backup (usually Publisher's VM only) is 50 IOPS.
*Nightly backup (usually Publisher's VM only) is 50 IOPS.
 +
 +
== Cisco Emergency Responder ==
 +
 +
100 IOPS is a good typical value to plan around.  Otherwise use values for Cisco Unified Communications Manager above (they will be conservatively high).
 +
 +
== Cisco Intercompany Media Engine ==
 +
 +
Use values for Cisco Unified Communications Manager above (they will be conservatively high).
== Cisco Unity Connection  ==
== Cisco Unity Connection  ==
Line 32: Line 38:
=== Summary of IOPS for Unity Connection  ===
=== Summary of IOPS for Unity Connection  ===
-
{| style="text-align: center; width: 75%" border="1"
+
{| border="1" style="text-align: center; width: 75%"
|-
|-
! IOPS Type  
! IOPS Type  
Line 81: Line 87:
The CUP 1000 user OVA generates about 60 IOPS during steady-state. Expect similar peaks as CUCM during backups and upgrades.  
The CUP 1000 user OVA generates about 60 IOPS during steady-state. Expect similar peaks as CUCM during backups and upgrades.  
-
<br>
+
<br>  
== Cisco Unified Attendant Consoles  ==
== Cisco Unified Attendant Consoles  ==
Line 87: Line 93:
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.  
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.  
-
{| border="1" cellspacing="1" cellpadding="1" width="1172"
+
{| width="1172" cellspacing="1" cellpadding="1" border="1"
|-
|-
-
| bgcolor="#cccccc" valign="middle" colspan="9" align="center" | '''LOAD TESTING'''
+
| valign="middle" bgcolor="#cccccc" align="center" colspan="9" | '''LOAD TESTING'''
|-
|-
-
| <br>
+
| <br>  
-
| valign="middle" colspan="3" align="center" | '''IOPS (Read)'''  
+
| valign="middle" align="center" colspan="3" | '''IOPS (Read)'''  
-
| <br>
+
| <br>  
-
| valign="middle" colspan="3" align="center" | '''IOPS (Write)'''  
+
| valign="middle" align="center" colspan="3" | '''IOPS (Write)'''  
| <br>
| <br>
|-
|-
-
| <br>
+
| <br>  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Max'''  
| valign="middle" align="center" | '''Max'''  
| valign="middle" align="center" | '''Average'''  
| valign="middle" align="center" | '''Average'''  
-
| <br>
+
| <br>  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Max'''  
| valign="middle" align="center" | '''Max'''  
Line 111: Line 117:
| valign="middle" align="center" | 1013.605  
| valign="middle" align="center" | 1013.605  
| valign="middle" align="center" | 0.442  
| valign="middle" align="center" | 0.442  
-
| <br>
+
| <br>  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 1112.87  
| valign="middle" align="center" | 1112.87  
Line 121: Line 127:
| valign="middle" align="center" | 320.006  
| valign="middle" align="center" | 320.006  
| valign="middle" align="center" | 3.691  
| valign="middle" align="center" | 3.691  
-
| <br>
+
| <br>  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 105.001  
| valign="middle" align="center" | 105.001  
Line 127: Line 133:
| Major upgrade
| Major upgrade
|-
|-
-
| bgcolor="#cccccc" valign="middle" colspan="9" align="center" | '''AVERAGE OPERATIONS'''
+
| valign="middle" bgcolor="#cccccc" align="center" colspan="9" | '''AVERAGE OPERATIONS'''
|-
|-
-
| <br>
+
| <br>  
-
| valign="middle" colspan="3" align="center" | '''IOPS (Read)'''  
+
| valign="middle" align="center" colspan="3" | '''IOPS (Read)'''  
-
| <br>
+
| <br>  
-
| valign="middle" colspan="3" align="center" | '''IOPS (Write)'''  
+
| valign="middle" align="center" colspan="3" | '''IOPS (Write)'''  
| <br>
| <br>
|-
|-
-
| <br>
+
| <br>  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Max'''  
| valign="middle" align="center" | '''Max'''  
| valign="middle" align="center" | '''Average'''  
| valign="middle" align="center" | '''Average'''  
-
| <br>
+
| <br>  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Min'''  
| valign="middle" align="center" | '''Max'''  
| valign="middle" align="center" | '''Max'''  
Line 149: Line 155:
| valign="middle" align="center" | 11.6  
| valign="middle" align="center" | 11.6  
| valign="middle" align="center" | 0.092  
| valign="middle" align="center" | 0.092  
-
| <br>
+
| <br>  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 561.05  
| valign="middle" align="center" | 561.05  
Line 159: Line 165:
| valign="middle" align="center" | 107.001  
| valign="middle" align="center" | 107.001  
| valign="middle" align="center" | 5.751  
| valign="middle" align="center" | 5.751  
-
| <br>
+
| <br>  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 0  
| valign="middle" align="center" | 50  
| valign="middle" align="center" | 50  
Line 166: Line 172:
|}
|}
-
<br>
+
<br>  
-
<br>
+
<br>  
== Contact Center  ==
== Contact Center  ==
-
=== [[Virtualization for Unified CCE|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.  
-
<br>
+
<br>  
{| class="wikitable FCK__ShowTableBorders"
{| class="wikitable FCK__ShowTableBorders"
Line 195: Line 201:
| '''Avg.'''  
| '''Avg.'''  
| '''95th Pct.'''  
| '''95th Pct.'''  
-
<br>
+
<br>  
|-
|-
Line 243: Line 249:
| 1,500  
| 1,500  
| 2,000 agents, 15 cps  
| 2,000 agents, 15 cps  
-
<br>
+
<br>  
|-
|-
Line 271: Line 277:
|}
|}
-
<br>
+
<br>  
=== [[Virtualization for Unified CCX|Contact Center Express/IPIVR IOPS]]  ===
=== [[Virtualization for Unified CCX|Contact Center Express/IPIVR IOPS]]  ===
Line 289: Line 295:
|}
|}
-
<br>
+
<br>  
=== [[Virtualization for Cisco MediaSense|Cisco MediaSense]]  ===
=== [[Virtualization for Cisco MediaSense|Cisco MediaSense]]  ===
Line 295: Line 301:
The following table lists the IOPS numbers for Cisco MediaSense partitions.  
The following table lists the IOPS numbers for Cisco MediaSense partitions.  
-
{| style="width: 513px; height: 228px" border="1" cellspacing="1" cellpadding="1"
+
{| cellspacing="1" cellpadding="1" border="1" style="width: 513px; height: 228px"
|-
|-
-
! scope="col" | Media Partitions<br>
+
! scope="col" | Media Partitions<br>  
! scope="col" | IOPS Specifications<br>
! scope="col" | IOPS Specifications<br>
|-
|-
|  
|  
-
Average IOPS for non-media partitions
+
Average IOPS for non-media partitions  
| 1700 ops/sec
| 1700 ops/sec
Line 315: Line 321:
|}
|}
-
<br>
+
<br>  
-
=== [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager Cisco Unfied Email Interaction Manager and Web Interaction Manager] ===
+
=== [http://docwiki-dev.cisco.com/wiki/Virtualization_for_Unified_Email_Interaction_Manager_-_Web_Interaction_Manager Cisco Unfied Email Interaction Manager and Web Interaction Manager] ===
-
{| border="1" cellspacing="1" cellpadding="1" width="800"
+
{| width="800" cellspacing="1" cellpadding="1" border="1"
|-
|-
-
| rowspan="2" | EIM-WIM compontnets
+
| rowspan="2" | EIM-WIM compontnets  
-
| colspan="3" | IOPS
+
| colspan="3" | IOPS  
| colspan="3" | Disk Read KBytes / sec  
| colspan="3" | Disk Read KBytes / sec  
| colspan="3" | Disk Write KBytes / sec
| colspan="3" | Disk Write KBytes / sec
|-
|-
-
| Peak
+
| Peak  
-
| 95th Pct.
+
| 95th Pct.  
-
| Avg.
+
| Avg.  
-
| Peak
+
| Peak  
-
| 95th Pct.
+
| 95th Pct.  
-
| Avg.
+
| Avg.  
-
| Peak
+
| Peak  
-
| 95th Pct.
+
| 95th Pct.  
| Avg.
| Avg.
|-
|-
Line 339: Line 345:
| 11.7  
| 11.7  
| 3.21  
| 3.21  
-
| 1.55
+
| 1.55  
-
| 51
+
| 51  
| 1  
| 1  
-
| 0.726
+
| 0.726  
| 103  
| 103  
-
| 19
+
| 19  
| 8.32
| 8.32
|-
|-
| File Server  
| File Server  
-
| 43.65
+
| 43.65  
| 25.23  
| 25.23  
-
| 14.36
+
| 14.36  
| 189  
| 189  
| 2  
| 2  
| 2  
| 2  
| 1769  
| 1769  
-
| 1025.9
+
| 1025.9  
| 446
| 446
|-
|-
| Database Server  
| Database Server  
-
| 736.9
+
| 736.9  
| 552  
| 552  
| 263.31  
| 263.31  
-
| 35450
+
| 35450  
| 23184  
| 23184  
-
| 3903
+
| 3903  
-
| 5737
+
| 5737  
| 2872  
| 2872  
| 1625
| 1625
Line 372: Line 378:
| 9.15  
| 9.15  
| 2.71  
| 2.71  
-
| 1.47
+
| 1.47  
-
| 57
+
| 57  
| 1  
| 1  
| 0.7  
| 0.7  
| 88  
| 88  
-
| 15.1
+
| 15.1  
| 8
| 8
|-
|-
| Services Server  
| Services Server  
-
| 11.15
+
| 11.15  
-
| 3.155
+
| 3.155  
| 1.53  
| 1.53  
-
| 55
+
| 55  
| 1  
| 1  
-
| 0.73
+
| 0.73  
-
| 1.89
+
| 1.89  
| 17  
| 17  
| 9
| 9
Line 395: Line 401:
| 3.36  
| 3.36  
| 1.43  
| 1.43  
-
| 55
+
| 55  
| 1  
| 1  
| 0.8  
| 0.8  
-
| 173
+
| 173  
| 21  
| 21  
| 10.24
| 10.24
|}
|}
-
&nbsp;
+
&nbsp;  
 +
 
 +
=== [http://docwiki-dev.cisco.com/wiki/Cisco_Unified_Intelligence_Center Cisco Unified Intelligence Center]  ===
 +
 
 +
*CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM.
 +
*Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs.
 +
*VM snapshots are not supported in production since they have significant impact on system performance.
 +
*The SAN must be able to handle the following Cisco Unified Intelligence Center application disk I/O characteristics.
 +
*Enable hyper threading on all ESXi servers. <br>
 +
 
 +
<br>
 +
 
 +
The following table lists the IOPS numbers for Cisco Unified Intelligence Center.<br>
 +
 
 +
{| cellspacing="1" cellpadding="1" border="1" style="width: 439px; height: 129px;"
 +
|-
 +
| Details<br>
 +
| Write (Kilobytes/Sec) <br>
 +
| Read (Kilobytes/Sec) <br>
 +
| IOPS <br>
 +
|-
 +
| Maximum <br>
 +
| 7758.00<br>
 +
| 466.00 <br>
 +
| 781.40 <br>
 +
|-
 +
| 95 Percentile <br>
 +
| 6446.30 <br>
 +
| 433.10 <br>
 +
| 628.34<br>
 +
|-
 +
| Average&nbsp; <br>
 +
| 5727.44<br>
 +
| 74.32<br>
 +
| 460.17 <br>
 +
|-
 +
| Minimum&nbsp; <br>
 +
| 4897.00<br>
 +
| 0.00<br>
 +
| 288.75 <br>
 +
|}
-
&nbsp;
+
<br><br>
-
&nbsp;
+
&nbsp;  
-
&nbsp;
+
&nbsp;  
-
{| class="wikitable" border="1"
+
{| 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]]
|}
|}

Revision as of 01:25, 28 October 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 nodes are setup with respect to service activation, redundancy groups, etc. (see www.cisco.com/go/ucsrnd for details).

CUCM storage access is on average 93-98% sequential writes with an IO block size of 4 kilobytes.

  • Active call processing: 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
  • 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 Emergency Responder

100 IOPS is a good typical value to plan around. Otherwise use values for Cisco Unified Communications Manager above (they will be conservatively high).

Cisco Intercompany Media Engine

Use values for Cisco Unified Communications Manager above (they will be conservatively high).

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.


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 template for Cisco Unified Attendant Consoles.

LOAD TESTING

IOPS (Read)
IOPS (Write)

Min Max Average
Min Max Average Operating Conditions
Cisco Unified Attendant Console Server 0 1013.605 0.442
0 1112.87 12.121 5,000 calls per hour, 25 concurrent operators, continuous LDAP sync, full logging
Upgrade 0 320.006 3.691
0 105.001 10.341 Major upgrade
AVERAGE OPERATIONS

IOPS (Read)
IOPS (Write)

Min Max Average
Min Max Average Operating Conditions
Cisco Unified Attendant Console Server 0 11.6 0.092
0 561.05 10.82 Synchronized directory, cached BLF, minimum online changes
Upgrade 0 107.001 5.751
0 50 3.57 Minor upgrade



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


Cisco Unfied Email Interaction Manager and Web Interaction Manager

EIM-WIM compontnets IOPS Disk Read KBytes / sec Disk Write KBytes / sec
Peak 95th Pct. Avg. Peak 95th Pct. Avg. Peak 95th Pct. Avg.
Application Server 11.7 3.21 1.55 51 1 0.726 103 19 8.32
File Server 43.65 25.23 14.36 189 2 2 1769 1025.9 446
Database Server 736.9 552 263.31 35450 23184 3903 5737 2872 1625
Messaging Server 9.15 2.71 1.47 57 1 0.7 88 15.1 8
Services Server 11.15 3.155 1.53 55 1 0.73 1.89 17 9
Web Server 11.2 3.36 1.43 55 1 0.8 173 21 10.24

 

Cisco Unified Intelligence Center

  • CPU usage (average) should not exceed 60% for the ESXi Server and for each of the individual processors, and for each VM.
  • Memory usage (average) should not exceed 80% for the ESXi Server and for each of the VMs.
  • VM snapshots are not supported in production since they have significant impact on system performance.
  • The SAN must be able to handle the following Cisco Unified Intelligence Center application disk I/O characteristics.
  • Enable hyper threading on all ESXi servers.


The following table lists the IOPS numbers for Cisco Unified Intelligence Center.

Details
 Write (Kilobytes/Sec)
Read (Kilobytes/Sec)
IOPS
Maximum
7758.00
 466.00
781.40
95 Percentile
6446.30
433.10
628.34
Average 
5727.44
 74.32
 460.17
Minimum 
4897.00
 0.00
 288.75



 

 

Back to: Unified Communications in a Virtualized Environment

Rating: 0.0/5 (0 votes cast)

Retrieved from "http://docwiki.cisco.com/wiki/Storage_System_Performance_Specifications"
Personal tools