GPA Manual

Description of GPA Reports
Guardian Performance Analyzer (GPA) Manual—135081
3-15
IPC Traffic Analysis
After the measurement is taken, enter:
+ LIST SERVERNET *
The latter command creates a structured data file named SVNET for GPA to analyze.
The IPC Traffic Analysis reports the ServerNet IPC information. This information points
out which processors create (send) and which consume (receive) messages. By moving
processes that create messages to the consuming CPUs, you can reduce interprocess
message traffic costs.
The line items are:
Example 3-12. IPC Traffic Analysis
1
NODE: \DOME DATE: 97/08/27 TIME: 16:51:49 MEASURE VERSION: G04
2
MEASUREMENT DATE: 97/08/27 TIME: 16:24:06 DURATION: 000:14:59
IPC Traffic Analysis CPU # 0
3 4 5 6 7 8 9 10 11 12
FM TO Read Read Read Read Write Write Write Write
NO NO Reqs Bytes Qtime QBusyt Reqs Bytes Qtime QBusyt
-- -- ------- ------------ ------- ------- ------- ------------ ------- -------
00 00 0 0 0.00 0.00 0 0 0.00 0.00
00 00 0 0 0.00 0.00 0 0 0.00 0.00
00 01 0 0 0.00 0.00 920 294680 845.00 705.00
00 02 0 0 0.00 0.00 0 0 0.00 0.00
00 03 0 0 0.00 0.00 0 0 0.00 0.00
01 00 43 644184 568.00 568.00 757 775316 764.00 100.00
02 00 0 0 0.00 0.00 0 0 0.00 0.00
03 00 0 0 0.00 0.00 0 0 0.00 0.00
-- -- ------- ------------ ------- ------- ------- ------------ ------- -------
-- -- ------- ------------ ------- ------- ------- ------------ ------- -------
43 644184 568.00 568.00 1677 1069996 1609.00 805.00
(1) NODE: The logical name used in the path to the physical device.
(2) MEASUREMENT: The date, time, and duration of the measurement.
(3) FM NO: The number of the linker CPU, which is the initiating processor of
IPC activity.
(4) TO NO: The number of the listener CPU, which is the replying or receiving
processor of IPC activity.
(5) Read Reqs: The number of requests that transferred data from this entity to
the processor.
(6) Read Bytes: The total number of bytes transferred as a result of read requests.
(7) Read Qtime: The total time spent by read requests queued for this entity.
(8) Read QBusyt: The time spent in a state in which requests for data transfer
from this entity to memory were queued.
(9) Write Reqs: The number of requests that transferred data from the processor
to this entity.