OpenEdge Management CPU utilization should typically be in the range of 1-5% (with possible spikes as noted below). Factors that might result in greater levels of CPU utilization include:
A very high number of monitored resources relative to the processing power of the host system — The number of resources you can monitor with OpenEdge Management before it introduces an unacceptable CPU load is very dependent upon the processing power of the host system.
On most systems monitoring a moderate number of resources such as 10 databases, 20 system resource monitors, and 20 network resource monitors, the CPU load of OpenEdge Management should be minimal. Host systems with greater processing power will be able to support greater resource counts.
A very short polling interval on monitored resources — Each poll of a resource requires a small measure of CPU utilization. Polling a lot of resources with very short polling intervals will increase OpenEdge Management load on the CPU. Using the default OpenEdge Management polling interval should minimize this problem.
If OpenEdge Management CPU utilization becomes a problem, you can reduce it by increasing the polling interval of monitored resources. For example, rather than polling databases every 5 minutes, you can set them to poll every 15 minutes.
A very high level of user interaction with OpenEdge Management through the management console — Each page displayed in the console needs to be produced by OpenEdge Management, and, therefore, requires a small measure of CPU utilization. A very high level of user interaction with the console will increase OpenEdge Management load on the CPU. This is especially true of any page that displays graphical data.
One feature to be particularly conscious of is the OpenEdge Management Auto Refresh capability. This feature allows you to configure the OpenEdge Management console such that the displayed pages are automatically refreshed at a specified rate. Automatically refreshing pages with lots of graphical data at a high frequency will increase OpenEdge Management load on the CPU. For details about the Auto Refresh feature, see Setting OpenEdge Management user preferences.
Very high levels of report execution — OpenEdge Management uses an OpenEdge database for storing trend information and ABL for running reports. This combination makes OpenEdge Management historical reports very efficient; however, running reports very frequently or against a large volume of historical data will increase OpenEdge Management load on the CPU.
You should use the OpenEdge Management scheduling facility to schedule reports to run at off-peak hours. You can also install a copy of OpenEdge Management on a nonproduction host and use it as the trend database for the OpenEdge Management install on your production hosts. Doing this will allow you to offload the management of trend data and run historical reports from your production host.
A large number of jobs — Like reports, jobs can put a heavy load on the CPU. The scheduling algorithm of your operating system might give all available CPU time to execute jobs or reports, which can cause a spike in CPU utilization while the job or report is running. You should schedule CPU-intensive jobs, such as database backups, to run at off-peak hours to minimize the chances of introducing too much overhead during peak system times. Offloading jobs to nonproduction systems is another option.
A very high number of monitored resources relative to the processing power of the host system — The number of resources you can monitor with OpenEdge Management before it introduces an unacceptable CPU load is very dependent upon the processing power of the host system.