Processor Time (CPUprcrProcessorTimePercent)


Displays the percentage of time that a processor is busy executing the threads of a process. Threads are units of work that make up a process. Consistently high numbers (greater than 75%) can indicate performance problems that can slow your system down. Temporary high percentages (spikes) for this parameter are normal. Under the _Total NT_CPU application instance, this parameter shows the total percentage of time that all processors are busy executing threads.

When in the alarm state, this parameter graph displays an annotation (usually denoted by *) that you can click to display the names of the top 10 processes that are using the most CPU resources.

Note

The Processor Time attribute in BMC ProactiveNet Performance Management is referred as the CPUprcrProcessorTimePercent parameter in BMC PATROL.

Recommendations

If this parameter is consistently greater than 75%, you should consider taking action to remedy the problem. Some suggestions include:

Reduce the workload of the CPU if possible — Review the processes running on your system:

  • Stop unneeded processes.
  • Review the processes listed in this parameter's graph annotation. You may find that processor cycles are being consumed by a poorly designed application that is not releasing system resources properly. In this case, you may need to contact the software vendor (or internal programmer) to get an updated version of the application.

Upgrade to a multiprocessor system — If your problem stems from hardware resources, upgrading to a machine with more than one processor might solve the problem.

Research possible hardware issues — There are several possibilities:

  • The SYSsysTotalInterruptsPerSec (device interrupts to the processor) parameter's value is greater than the SYSsysSystemCallsPerSec (calls to system service routines) parameter's value, then a hardware device is probably generating excessive interrupts and degrading performance.
  • If the SYSsysTotalInterruptsPerSec parameter's value is greater than 1000, an I/O device is probably generating these interrupts.
  • You may find that a disk controller that requires a large amount of physical I/O is consuming the processor cycles. In this case, you can install a DMA disk controller to reduce processor utilization.
  • If a memory bottleneck exists, the increased paging activity may be taxing the processor and masking what is primarily a memory bottleneck instead of a processor bottleneck. Refer to the following NT_MEMORY parameter topics to help determine if you have a memory bottleneck:  MEMmemAvailableBytes, MEMmemPageFaultsPerSec, and MEMmemPagesPerSec.

Thresholds for alarms and warnings

Item

Default Threshold

State

Border

0-100

undefined

Alarm 1

90-95 percent

warn

Alarm 2

95-100 percent

alarm

Consider adjusting these settings to suit the needs of your system. Refer to baselining overview for information about how to determine your system's characteristics and needs.

Default properties

Property

Default value

BMC PATROL properties

Application class

NT_CPU

Command type

not applicable

Icon style

graph

Unit

percentage

Border range

undefined

Alarm1 range

undefined

Alarm2 range

undefined

Scheduling (poll time)

inherits poll time of collector

Active at installation

yes

Parameter type

consumer

Value set by

CPUProcessorColl

BMC ProactiveNet Performance Management properties

Monitor type

Processor

Key Performance Indicator

Yes

Monitor for abnormalities

Yes

Graph by default

Yes

Availability

No

Response time

No

Normal distribution

Yes

Statistical

Yes

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*