|
Measures reported by PoaClientSvrTest
This
test reports performance metrics pertaining to the client connections to a
Groupwise Post Office Agent (POA) service.
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Request_rate
|
The rate at which
client/server requests were received during the last measurement
period |
Reqs/Sec
|
A high value may be indicative of an excessive load on the POA
|
| Pending_requests
|
The number of
Client/Server requests pending |
Number
|
If this value is high, increase the number of POA threads so that more
users can be serviced by the POA.
|
| Users_timeout
|
The number of
user sessions that timed out during the last measurement period. This
can be calculated by:
(Current measure – Previous measure) |
Number
|
Session timeouts do not indicate a problem with the POA, but rather a
problem with the users. Users who have timed out are users for which
the POA has closed the connection because the GroupWise client was no
longer communicating. Timed out users may not be exiting GroupWise
normally or may be having other problems with their workstations.
|
| Msgs_in_queue
|
The number of
messages in the queues |
Number
|
If this value is high, you can increase throughput for the message
queues using the /FAST4 startup switch of the MTA. This causes the MTA
to monitor and process the high priority messages separately from the
normal and low priority messages. This helps avoid bottlenecks in the
processing of administrative messages and high priority user messages
versus normal and low priority user messages.
|
| Users_connected
|
The number of
connected user sessions |
Number
|
|
|