Expand Configuration and Management Manual (H06.21+, J06.10+)

Tuning
Expand Configuration and Management Manual — 529522-013
19 - 8
Application Message Size
As shown in Figure 19-2 on page 19-7, QIO recognizes that the data is to be sent to an
application that is not on the local node, and it routes the request to the appropriate
Expand line-handler process.
If the Expand packet size is large enough to hold all the message from the application,
the Expand line-handler process puts the message into a single packet. If the Expand
packet size is smaller than the message that the application wants to send, the Expand
line-handler process must send more packets across the message system to the
NonStop TCP/IP process.
Expand Subsystem Overhead
It is important to consider Expand subsystem overhead when using facilities with
limited bandwidth. Application message size and Expand packet size have significant
effects on subsystem overhead. The number of Expand packets required for an
application message is calculated using this formula:
app_msg
is the user message size in bytes.
fsm
represents the file system and Expand message header information (in bytes) sent
at the start of each message.
packet_size
is the maximum number of bytes per packet. If the variable packet size feature is
used, packet_size is the PATHPACKETBYTES modifier value; otherwise,
packet_size is equal to (frame_size - 4 )* 2 where frame_size is the
FRAMESIZE modifier value. The default is 256.
pkt
represents the Expand Layer 2 and packet header information (in words) sent at
the start of every Expand frame.
The values of fsm and pkt vary according to the oldest version of the Expand
subsystem at the originating and destination nodes.
1 + $INT((app_msg + fsm) / (packet_size - pkt))