TS/MP System Management Manual (G06.24+, H06.03+)

Configuring Objects in a PATHMON Environment
NonStop TS/MP System Management Manual—541819-001
3-30
Steps to Optimum Link Configuration
The calculation must be done for each transaction; then the results are applied to each
serve class. The formula is:
avg. transaction vol. x constant = working avg. transaction vol.
For example:
30 transactions per second x 1.5 = 45 transactions per second
(tps)
where “1.5” is the safety factor and the working average transaction volume is
expressed in transactions per second.
Step 4 Measure Server Class Response Time
Assuming that each server class provides one service, use the Measure product to
determine server class response time.
Step 5 Calculate Active Links for Each Transaction
For each transaction type that accesses the server class, calculate the number of
active links required by that transaction type.
working avg. transaction vol. x server class process response
time = active links
where active links is transactions of a given type in progress in the server class,
working avg. transaction vol. is the result of your calculation in Step 3, and
server class process response time is the result of Step 4.
In this example, “45 tps” is the working average transaction volume from Step 3, and
“2 seconds” is the server class response time as measured.
45 tps x 2 seconds = 90
The transaction type requires 90 active links to the server class.
Step 6 Calculate Total Active Links: the MAXSERVERS
attribute
Now add the active links for all the transactions that use the server class to get a figure
for the total active links the server class must support. This figure is the value you
specify for the MAXSERVERS attribute for the server class. MAXSERVERS specifies
the number of server processes that must be able to run in the server class at the
same time to satisfy potential demand for active links.
Note. Because Steps 4-6 must be calculated on a per-server-class basis, a spreadsheet could
be helpful to record and calculate the required values.
Note. A transaction type may access more than one server class to complete the transaction.
The transaction may even access a given server class more than once. Be sure to account for
all transaction accesses when making this calculation.