Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on November 3, 2025. We recommend that you use PATROL for Linux, PATROL for AIX, or PATROL for Solaris to monitor operating systems.

Length of Run Queue (CPURunQSize)


Description

This parameter displays the number of processes in the run queue (RunQ). This parameter is more useful for systems that do not support the uptime command and therefore do not support the CPULoad parameter. CPULoad reports an average number of processes while CPURunQSize reports the current number of processes in the run queue.

Note

On HP-UX systems, SAR occasionally outputs a null value that can lead to incorrect values for the CPURunQSize parameter.

The data from this parameter is often more useful when looked at in combination with other parameters (such as CPUCpuUtil ). A high load along with low CPU utilization can indicate problems (most likely in the I/O subsystem).

Recommendations

A consistently high load can indicate performance bottlenecks in one or more of the following three areas:

  1. Memory: If the number of page faults (MEMPFault) and/or page-outs (MEMPageOut) is high and your load is high, your system probably needs more memory to improve performance.
  2. Disk/controllers: If your load is high and the CPU has excessive waits for I/O operations (CPUWio), then your system could probably benefit by adding a controller and/or disk drive.
  3. CPU: If items 1 and 2 above are normal, then you may have reached the limit of your system's resources. The following suggestions may help:

    • If your CPU load is high and a particular process that is important to you is not executing quickly enough, you could use the renice command to increase the process' priority. Refer to your system's documentation for information on the renice command.
    • If you have batch processes running, you could schedule some jobs to run during non-peak times.
    • If the previous bulleted items do not help, you may need to upgrade your system's CPU capacity.

Range Thresholds

Because each UNIX system may have vastly different characteristics, no range thresholds have been set by default. With the combination of your experience with your system and your system documentation, you can set ranges that are useful.

Default parameter attributes

Attribute

Default value

Application class

CPU

Command type

not applicable

Platform

all

Icon style

graph

Unit

number of processes

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

DCMColl controlled by CPUCtrl

SARColl or VMColl

BMC ProactiveNet Performance Management properties

Property

Default value

Monitor type

CPU

Key Performance Indicator

No

Monitor for abnormalities

No

Graph by default

No

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*