Cisco Cisco Process Orchestrator 3.0 Guida All'Installazione
1-7
Cisco Process Orchestrator Installation Guide
OL-24931-02
Chapter 1 Installation Prerequisites
Cisco Process Orchestrator Performance Best Practice Guidelines
The disk space requirements formula as shown in the following table is based on the reporting database
running 5000 processes per day and 500 tasks for 6 months retention:
running 5000 processes per day and 500 tasks for 6 months retention:
Cisco Process Orchestrator Performance Best Practice
Guidelines
Guidelines
Cisco Process Orchestrator's multi-threaded architecture allows it to fully utilize all processors on the
Cisco Process Orchestrator server system. Cisco Process Orchestrator generally scales linearly with the
number of processor cores and the clock speed at which processors execute. Adding more CPU cores is
the single most effective factor in increasing Cisco Process Orchestrator performance. To maximize
performance capacity, include the maximum number of processor cores available in the hardware
supporting the Cisco Process Orchestrator server.
Cisco Process Orchestrator server system. Cisco Process Orchestrator generally scales linearly with the
number of processor cores and the clock speed at which processors execute. Adding more CPU cores is
the single most effective factor in increasing Cisco Process Orchestrator performance. To maximize
performance capacity, include the maximum number of processor cores available in the hardware
supporting the Cisco Process Orchestrator server.
The Cisco Process Orchestrator server intelligently caches data such as actively running processes to
optimize performance. Sufficient memory is required to minimize paging. Allow memory to handle burst
situations, but plan the number of processor cores in the system to be sufficient for steady state (average)
load.
optimize performance. Sufficient memory is required to minimize paging. Allow memory to handle burst
situations, but plan the number of processor cores in the system to be sufficient for steady state (average)
load.
Database optimization is very important. While Cisco Process Orchestrator ships with a schema, which
is performance optimized, including the relevant indices, customers need to install and operate this
database. Customers should refer to documentation associated with their chosen database platform for
best practice.
is performance optimized, including the relevant indices, customers need to install and operate this
database. Customers should refer to documentation associated with their chosen database platform for
best practice.
In high performance scenarios, the following best practices can dramatically affect performance:
•
A separate host server for the database versus other Cisco Process Orchestrator architectural
elements
elements
•
A separate high speed disk for the database, operating system and program files, and swap files
•
Sufficient memory to avoid paging
A high speed network connection typically means the database is "close by" the Cisco Process
Orchestrator server, or possibly in the same data center.
Orchestrator server, or possibly in the same data center.
Proper database server hardware and routine database maintenance can have substantial effects on
performance. Planning for high availability can have impacts on system design, requirements,
environments, and installation topologies.
performance. Planning for high availability can have impacts on system design, requirements,
environments, and installation topologies.
Cisco Process Orchestrator Ports and Services
This section provides the active ports and services used by Cisco Process Orchestrator as well as the
recommended Exchange ports for use when executing targets.
recommended Exchange ports for use when executing targets.
Table 1-6
Calculating Disk Space Formula
Data
Formula
Task Size
1000 KB / day x 6 months = 180 MB
Process Audit Size
1000 KB / day x 6 months = 180 MB
Task Audit Size
75 KB / day x 6 months = 13.5 MB
Total Size
DB initial size for 6 months retention = 180 MB + 180 MB +
13.5 MB = 373.5 MB (0.4 GB)
13.5 MB = 373.5 MB (0.4 GB)