| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Pct_agents_waiting
|
Indicates the
percentage of agents waiting to execute a unit of work. |
Percent
|
It
shows the percentage of agents that are waiting to execute (that is,
that are asleep). Use this measure to adjust the MAXCAGENTS parameter
setting for the database. If this value
is high, you may consider increasing the MAXCAGENTS parameter. |
| Pct_piped_sorts_accepted
|
Indicates the
percentage of piped sorts accepted during the interval. |
Percent
|
Piped
sorts reduce disk I/O and tend to be more efficient. A high percentage
of piped sorts accepted indicate that efficient sorts are being
performed. A low percentage indicates that sort heap and sort heap
threshold may have to be adjusted. If this percentage is low, then
increase the SHEAPTHRES parameter and possibly the SORTHEAP parameter. |
| Pct_piped_sorts_rejected
|
Indicates the
percentage of piped sort requests that were rejected. |
Percent
|
Piped
sorts reduce disk I/O and tend to be more efficient. A low percentage
of piped sorts rejected indicates that efficient sorts are being
performed. A high percentage of piped sorts rejected indicates that
sort heap and sort heap threshold may have to be adjusted. If this
percentage is high, then increase the SHEAPTHRES parameter and
possibly the SORTHEAP parameter. |
| Agents_registered
|
Indicates the
number of agents registered in the database manager instance that is
being monitored (coordinator agents and subagents). |
Number
|
This
measure can be used to evaluate your setting for the MAXAGENTS
configuration parameter. |
| Pct_agents_from_empty_pool
|
Indicates how
often an agent must be created because the pool is empty. |
Percent
|
A
high value may indicate that the NUM_POOLAGENTS configuration
parameter should be increased. A low value suggests that
NUM_POOLAGENTS is set too high, and that some of the agents in the
pool are rarely used and are wasting system resources.
A high percentage can also
indicate that the overall workload for this node is too high. The
workload can be adjusted by lowering the maximum number of
coordinating agents specified by the MAXCAGENTS configuration
parameter, or by redistributing data among the nodes.
|