Storage System Performance Specifications
m (1 revision)
Revision as of 20:13, 5 August 2011
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
The CUP 1000 user OVA generates about 60 IOPS during steady-state. Expect similar peaks as CUCM during backups and upgrades.
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.|
|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|
The following table lists the IOPS numbers for Unified Contact Center Express/IPIVR.
|IOPS Avg per VM||150|
|IOPS Max spike per VM||1500|
The following table lists the IOPS numbers for Cisco MediaSense partitions.
| Media Partitions|| IOPS Specifications|
Average IOPS for non-media partitions
|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|