Tandem Capacity Model (TCM) Manual

Figure 35 CPU Workload Apportionment Screen
Significant Rows
1. CPU Config—Not directly modifiable
CPU Config is the actual CPU configuration that was measured for the sample. The configuration
includes the number of CPUs, type and the IPU information. For single core CPUs, the IPU field
would contain "NA". If the sample was measured on an HP NonStop system running the G06
RVU, the suffix G06 is displayed next to the CPU type.
The WA model permits only one CPU type to perform its calculations. If the sample was
measured on a mixed system (using NSR-W and NSR-G processors, for example), CPU seconds
are normalized by MeasTCM to one CPU type, as specified in the MeasTCM control file on
the NonStop host system. For this reason, the number of CPUs might be fractional if the sample
was measured on a mixed system.
2. Fixed CPU Seconds—Not directly modifiable
Fixed CPU Seconds is the total number of CPU seconds consumed per second by process
categories of type F (fixed). This number is not included in the CPU and disk consumption of
individual transactions, but does affect the total CPU and disk utilizations. Define a category
as type F if its CPU and disk consumption do not increase as throughput increases, such as
during asynchronous data communications polling activity or the running of Measure.
3. Apportionment—Not modifiable
Apportionment indicates the apportionment method used by the WA screen. The apportionment
method name is the name of the apportionment table file (without the .AWA extension) that
was used to generate the apportionment formulas when Workload Apportionment was selected
from the Update tab.
Significant Columns
4. Txn Name—Modifiable by the TCM administrator
Txn Name is the name of the transaction as defined on the NonStop host system using
MeasTCM. In MeasTCM, you can specify the transaction names for each transaction in the
application or applications being modeled. You can specify up to 40 transactions. For more
information, see “Customizing Your Process Category Control File” (page 33).
If no transaction names are specified in MeasTCM, TCM assumes that each server category
(type S) represents a transaction and uses the corresponding server category names as
transaction names.
The TCM administrator can modify the transaction names.
5. First Unlabeled Column—Not directly modifiable
The first unlabeled column shows the type of a transaction: X for OLTP transactions, B for batch
transactions, or Q for query transactions.
CPU Workload Apportionment Screen 109