NET/MASTER Management Services (MS) Command Reference Manual

LBANNER
PARAM CPUWEIGHT
NonStop NET/MASTER MS Commands
2–206 115412 Tandem Computers Incorporated
3. In a configuration file, the following example specifies weights for 16 CPUs
(0 through 15):
PARAM CPUWEIGHT=( 0, 20)
PARAM CPUWEIGHT=( 1,100)
PARAM CPUWEIGHT=( 2, 30)
PARAM CPUWEIGHT=( 3,100)
PARAM CPUWEIGHT=( 4, 40)
PARAM CPUWEIGHT=( 5,100)
PARAM CPUWEIGHT=( 6, 50)
PARAM CPUWEIGHT=( 7,100)
PARAM CPUWEIGHT=( 8, 60)
PARAM CPUWEIGHT=( 9,100)
PARAM CPUWEIGHT=(10, 70)
PARAM CPUWEIGHT=(11,100)
PARAM CPUWEIGHT=(12, 80)
PARAM CPUWEIGHT=(13,100)
PARAM CPUWEIGHT=(14, 90)
PARAM CPUWEIGHT=(15,100)
In this example, odd-numbered CPUs are configured for maximum availability,
while even-numbered CPUs are partially available.
4. Assume that CPU 0 is assigned a weight of 50 during NonStop NET/MASTER MS
startup. Assume that a dynamic process with a process weight of 30 starts in
CPU 0 after NonStop NET/MASTER MS startup. The availability of CPU 0 is now
20 (50 less 30).
Assume that you use the following command to configure CPU 0 with a
weight of 90:
PARAM CPUWEIGHT=(0,90)
CPU 0 is available to one or more dynamic processes whose individual or
combined process weight, respectively, is 60 or less (90 less 30). If the dynamic
process currently using CPU 0 stops, the weight of CPU increases to 90.
5. Assume that CPU 0 is assigned a weight of 70 during NonStop NET/MASTER MS
startup. Assume that a dynamic process with a process weight of 40 starts in
CPU 0 after NonStop NET/MASTER MS startup. The availability of CPU 0 is now
30 (70 less 40).
The following command now makes CPU 0 unavailable to all new processes, but
has no effect on the dynamic process currently using CPU 0:
PARAM CPUWEIGHT=(0,0)
If the dynamic process currently using CPU 0 stops, CPU 0 remains unavailable to
all new processes.