GPA Manual for G-series RVUs

Guardian Performance Analyzer (GPA) Manual – (544977-001) Page 50 of 106
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
The line items are:
(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 (“From Number”).
(4)
TO NO: The number of the listener CPU, which is the replying or
receiving processor of IPC activity (“To Number”).
(5)
Read KReqs: The number of requests, in thousands, that
transferred data from this entity to the processor.
(6)
Read KBytes: The total number of kilobytes transferred as a result
of read requests.
(7)
Rsecs Qtime: The total time spent by read requests queued for this
entity, in seconds.
(8)
Rsecs QBusy: The time spent in a state in which requests for data
transfer from this entity to memory were queued, in seconds.
(9)
Write KReqs: The number of requests, in thousands, that
transferred data from the processor to this entity.
(10)
Write KBytes: The total number of kilobytes transferred as a result
of write requests.
(11)
WSecs Qtime: The total time spent by write requests queued for this
entity, in seconds.
(12)
WSecs QBusyt: The time spent in a state in which requests for data
transfer from memory to this entity were queued, in seconds.
If applicable, there will be a small section after the IPC traffic analysis tables listing the
processes whose $RECEIVE queue lengths may be indicative of configuration
problems.