Hp Integrity NonStop J-Series Manuel d'utilisateur télécharger pdf (Page 66)

Guardian Performance Analyzer (GPA) User Guide – (544541-006) Page 66 of 131

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.

Example 3-12. Processes with $RECEIVE queue lengths with Problems

The following processes are exhibiting a $RECEIVE queue length that

may indicate an application/application-configuration problem:

0,433 $X0BS6 $SYSTEM SYS02 LOGIN 0.00% MSG/s: 0 Q-LEN: 1.91

0,514 $X0BTA $SYSTEM SYS02 LOGIN 0.00% MSG/s: 0 Q-LEN: 1.84

0,694 $X0BSP $SYSTEM SYS02 LOGIN 0.00% MSG/s: 0 Q-LEN: 1.92

0,743 $X0BST $SYSTEM SYS02 LOGIN 0.00% MSG/s: 0 Q-LEN: 1.69

[Back to TOC]

1 2 ... 61 62 63 64 65 66 67 68 69 70 71 ... 130 131

Pas de commentaire

Hp Integrity NonStop J-Series Manuel d'utilisateur Page 66