Cisco Cisco Customer Response Solution Downloads 设计指南
7-3
Cisco IPCC Express Solution Reference Network Design
9560890308
Chapter 7 Sizing the Cisco CallManager Servers
Impact of IPCC Express on the Cisco CallManager Performance
–
Standard
–
High Performance
The following performance observations are based on scalability and load testing of Cisco CallManager
servers with the IPCC Express application. Various simple and complex call flow scenarios were used.
In all tests conducted, CPU measurements were taken for each individual resource that added up to the
total CPU consumption required to process the call load. The CPU percentages stated in
servers with the IPCC Express application. Various simple and complex call flow scenarios were used.
In all tests conducted, CPU measurements were taken for each individual resource that added up to the
total CPU consumption required to process the call load. The CPU percentages stated in
, are
all relative to each other regardless of load. These percentages may vary from one release to the next,
and are not to be used to manually configure and size Cisco CallManager servers. The intent is to give
you an idea of the relative CPU weight of each resource if it were configured/registered in one Cisco
CallManager node by itself. Hence, it is important to balance all resources equally as much as possible
if you are using more than one primary Cisco CallManager server. This balancing of resources prevents
overloading one server at the expense of another.
and are not to be used to manually configure and size Cisco CallManager servers. The intent is to give
you an idea of the relative CPU weight of each resource if it were configured/registered in one Cisco
CallManager node by itself. Hence, it is important to balance all resources equally as much as possible
if you are using more than one primary Cisco CallManager server. This balancing of resources prevents
overloading one server at the expense of another.
Table 7-1
Effect of Major Performance factors/criteria on CCM CPU resources with IPCC and IVR applications
Performance Criterion
Effect on CCM System
CTI Route Points
•
CPU resource consumption: Very low.
•
The portion of the CPU consumed by the CTI route points is about 3% of the total
CPU consumption. This result is mainly because the route point is only
redirecting calls and not terminating media (In CCM 4.x, route points are capable
of terminating media and the CPU consumption will vary based on use
scenarios.)
CPU consumption. This result is mainly because the route point is only
redirecting calls and not terminating media (In CCM 4.x, route points are capable
of terminating media and the CPU consumption will vary based on use
scenarios.)
CTI Manager (JTAPI monitoring)
•
CPU resource consumption: Low.
•
The portion of the CPU consumption by the CTI Manager averaged about 10%.
This included both JTAPI users monitoring agents and JTAPI users monitoring
CTI ports (all resources monitored were not in this node).
This included both JTAPI users monitoring agents and JTAPI users monitoring
CTI ports (all resources monitored were not in this node).
IPCC Agent Phones
•
CPU resource consumption: Low.
•
The portion of the CPU consumed by the IPCC agent phones is about 10% of the
total CPU consumption. This only includes the phone portion similar to any other
IP Phone.
total CPU consumption. This only includes the phone portion similar to any other
IP Phone.
IVR ports used with either self service
or with IPCC Express for call
treatment before transferring calls to
agents or other devices.
or with IPCC Express for call
treatment before transferring calls to
agents or other devices.
•
CPU resource consumption: Moderate.
•
The portion of the CPU consumed by the CTI ports was 20% on average of the
total CPU consumption. This does not include the CTI Manager portion of the
application monitoring the CTI ports (see CTI Manager)
total CPU consumption. This does not include the CTI Manager portion of the
application monitoring the CTI ports (see CTI Manager)
GW ports
•
CPU resource consumption: Heavy.
•
The portion of the CPU consumed by the gateway ports is about 56% of the total
CPU consumption.
CPU consumption.
Total CPU load distribution for all the
above resources
above resources
Distribution of CPU load for the above five major resources based on where they were
registered:
registered:
•
3%—Incoming Route Points
•
10%—CTI Manager/JTAPI
•
10%—Agent Phones
•
20%—CTI Ports
•
57%—Gateway Ports