Guardian Performance Analyzer (GPA) User Guide
Guardian Performance Analyzer (GPA) User Guide – (544541-006) Page 49 of 131 
Global Performance Indicators 
In this subsection of the report (Example 3-3), GPA provides an overall evaluation of the 
system‟s performance based on the GPA analysis criteria. For the node in the 
example, the GPA analysis has found the following conditions: 
Example 3-3. Global Performance Indicators 
III. GLOBAL PERFORMANCE INDICATORS 
 1
 EXCESSIVE DISPATCHING : NO 
 2
 INDEX LEVELS > 2  : NO 
 3
 PROCESSOR LOAD BALANCE : POOR 
 4
 OVER UTILIZED DISK  : NO 
 5
 OVER UTILIZED NODE : NO 
 6
 CACHE FAULT DETECTED : NO 
 7
 OVER UTILIZED CPU  : NO 
 8
 TRANSIENT PROCESSING : NO 
 9
 DISK VOLUME QUEUING : YES 
10
 BLOCKED REQUESTS  : NO 
11
 AVERAGE CACHE HIT % : 83.20% 
12
 TOTAL CACHE CALL RATE: 25.00 /SEC 
(1) 
EXCESSIVE DISPATCHING: No excessive dispatching. A dispatch 
occurs each time CPU cycles are allocated to a process. The 
acceptable value for this parameter depends on the CPU type. 
(2) 
INDEX LEVELS > 2: No index levels greater than 2. Each index level in 
a key-sequenced file can cause an additional physical I/O operation 
and/or additional CPU cycles. Keeping the number of index levels at 
a minimum (no more than 2) reduces the number of physical I/O 
operations and/or CPU cycles required for each logical I/O operation 
on the file. 
(3) 
PROCESSOR LOAD BALANCE:  Poor processor load balance. Referring 
to Example 3-1 shows that the node has two CPUs that are out of 
balance. 
(4) 
OVER UTILIZED DISK: No over utilized disk process. None of the 
percentage busy times for the disk processes on the node is 
excessive. 
(5) 
OVER UTILIZED NODE: No over utilization of the node. The percentage 
utilization of the node is below the maximum recommended level 
(refer to Example 3-1). 
(6) 
CACHE FAULT DETECTED: No cache faults detected. A cache fault 
occurs when a disk process expects to find a data block in cache and 
discovers that the memory manager has removed it. The memory 
manager does this whenever it needs the extra storage space to 
relieve a shortage of main memory. 










