Analyze Performance › Brief Analysis Reports › Interpret the Brief Analysis Report

Interpret the Brief Analysis Report

The following example is an example of a Brief Analysis Report. A description of each item in the report headings follows the example.

The following statements are keyed to the columns in the report example:

1. Rule identifier.
2. For this reporting period, the percentage of time that the conditions of a rule were satisfied.
3. Number of records satisfying rule occurrences.

Rules in Summary domain do not provide data in columns 2 and 3 because their conditions are based on data averaged over the entire analysis period.

Brief Analysis                       CLUSTER                            Page   1
							PA Vx.x
		Saturday 01-OCT-2006 00:00 to 23:00

						NODE: DEMAND
ID  %oftime Recds       One Line Description
-----  ----- ----  ------------------------------------
  1       2    3
M0010   0.3    1  Application program pagefaults very heavily.
M0500   0.3    1  Heavy paging, increase the working set extent for user(s).
R0270   0.6    2  Process(es) hung in AST.  (See full report.)
I0160   1.2    4  Window turns are too high, alleviate file fragmentation.
R0070             More resources than hash table entries; increase RESHASHTBL.
R0300   0.3    1  Lots of contention for distributed locks.

Summary for DEMAND: 6 rules fired; of 337 records, 8 satisfied conditions.

NODE: SUPPLY
ID %oftime Recds       One Line Description
----- ----- ----  ------------------------------------
R0095     6   22  Low hit ratio, high attempt rate on the file header cache.
R0300     0    1  Lots of contention for distributed locks.

Summary for SUPPLY: 2 rules fired; of 338 records, 23 satisfied conditions.

Summary for VOLTY: 0 rules fired; of 337 records, 1 satisfied conditions.

						CLUSTER
ID %oftime Recds       One Line Description
----- ----- ----  ------------------------------------
L0050          1  I/O bottleneck on disk; reduce or redistribute load.

Summary for CLUSTER:      1 Rules fired.