Here is an example of how the low-, medium-, and high-performance levels are set.
User Bob belongs to the low-performance class. User Tom belongs to the medium-performance
class. User Mary belongs to the high-performance class. If you wanted to assign different
server values to low, medium, and high users, you would define the following entities
in the spdsserv.parm parameter file:
SORTSIZE=256M;
BINBUFSIZE=32K;
MAXWHTHREADS=4;
WORKPATH="/var/tmp";
---MED---
SORTSIZE=512M;
MAXWHTHREADS=6;
---HIGH---
SORTSIZE=1G;
MAXWHTHREADS=6;
WORKPATH="/var/hightmp";
Here’s what happens in the spdsserv.parm parameter file:
-
Low users receive the unlabeled
values for SORTSIZE=, BINBUFSIZE=, MAXWHTHREADS=, and WORKPATH=.
-
Medium users get the unlabeled
values, with the exceptions of the SORTSIZE= setting, which has a
value of 512 MB, and the MAXWHTHREADS= setting, which has a value
of 6 GB.
-
High users get the unlabeled values,
with the following exceptions: the SORTSIZE= setting, which has a
value of 1 GB; the MAXWHTHREADS= setting, which has a value of 6 GB;
and the WORKPATH= setting, which has a value of /var/hightmp.
All initial values
for each performance class are inherited from the unlabeled settings.
However, settings from the labeled classes are not inherited. Users
who are set to HIGH do not inherit any parameter settings from the
MED level. Therefore, you must specify MAXWHTHREADS=6 for the HIGH
and MED levels.
The LOCKING=YES setting is a special user case. All users share the same SPD Server
locking proxy. For LOCKING=YES, all users get the unlabeled values in the spdsserv.parm
parameter file, regardless of their performance class. You can use the following code
to override
the parameter values for all users of the locking proxy.
SORTSIZE=256M;
BINBUFSIZE=32K;
MAXWHTHREADS=4;
WORKPATH="/var/tmp";
---MED---
SORTSIZE=512M;
MAXWHTHREADS=6;
---HIGH---
SORTSIZE=1G;
MAXWHTHREADS=8;
WORKPATH="/var/hightmp";
---LOCKING---
MAXWHTHREADS=2;
In this example, all
LOCKING=YES users inherit the unlabeled parameter values, with the
exception of the initial MAXWHTHREADS=4 setting, which changes to
MAXWHTHREADS=2.