OSI/FTAM Configuration and Management Manual

Planning, Installing, and Configuring Tandem FTAM
OSI/FTAM Configuration and Management Manual—421944-001
3-33
Controlling System Performance
Controlling System Performance
The following object attributes affect the performance of your Tandem FTAM
implementation, as described in the following subsections:
•
Number of Process Assocations and Attaches on this page
•
Maximum Number of Configurable Processes on page 3-34
•
Execution Priority on page 3-34
•
Regeneration of Subdevices on page 3-35
•
Resource Allocation Interdependencies on page 3-36
By manipulating these attribute values, you can redistribute the workload to handle
changes in demand for services. Experiment to find the best values for your installation.
In addition, configuration attributes set in your underlying OSI/AS subsystem(s) can
affect performance. For details, see the OSI/AS Configuration and Management Manual.
Number of Process Assocations and Attaches
The maximum number of associations allowed for an initiator or responder process can
significantly affect system performance. You can specify this number by using the
MAXASSOC attribute of the PROCESS object. For initiator processes, this attribute
specifies the maximum number of concurrent associations that can occur between the
initiator and user applications. For responder processes, this attribute specifies the
maximum number of associations that can occur between OSI/AS and the responder. For
both types of processes, the attribute has a value in the range of 1 to 32 and defaults to 8.
For example, to allow the initiator $FTI1 to service up to 16 associations, you could
configure the process with the following command:
ADD PROCESS $AMGR.#FTAMI.FTI1, NAME $FTI1, COMNAME "FTMI1A",&
MAXASSOC 4
Set the MAXASSOC attribute according to how many simultaneous association requests
you want your processes to handle. Keep in mind that if the MAXASSOC value is too
low, you may be forced to create a large number of processes to service requests. If the
MAXASSOC value is too high, the processes may be overworked trying to service all of
the requests. The optimal setting depends upon how you want work distributed within
your particular installation.
In addition to the MAXASSOC attribute, responder processes have a MAXATTACH
attribute, which specifies the maximum number of outstanding attaches that can be
posted to OSI/AS by the responder. This number also determines the number of
subdevices created for the responder process. This attribute has a value in the range of 1
to the MAXASSOC value, whichever is lower, and defaults to 8. Under most
circumstances, you should set the MAXATTACH attribute to the same value as
MAXASSOC.