HP NonStop G-Series - Manual (Page 41)

Preparing to Use SMF
HP NonStop Storage Management Foundation User's Guide—523562-008
2-7
Memory Resource Impact
Memory Resource Impact
Memory for SMF processes is allocated in two ways: the first swap file is created by
the Kernel-Managed Swap Facility (KMSF), and the extended swap file is created as a
conventional swap file on the $SYSTEM disk. Following are memory requirements for
SMF components:
These figures are for individual processes only and must be doubled to account for a
primary/backup process pair. When first configured, the backup processes use
substantially less memory than listed; however, upon takeover the additional space is
allocated and never released.
You can calculate the amounts of conventional and KMSF swap space required for a
CPU by counting the number of primary and backup SMF processes located in that
CPU and multiplying by the per-process amounts by using this formula:
KMSF = number of $ZSMS processes * 3.2 + number of pool
processes * 2.4 + number of VDPs * 4.2
conventional memory = number of $ZSMS processes * 2.0 +
number of pool processes * 2.0
For example, one $ZSMS process, two pool processes, and four VDPs would require
24.8 MB of kernel-managed swap space, and 6.0 MB of conventional swap space.
Operational Impact of Using SMF
Introducing SMF virtual disks on a system has an operational impact in the following
areas:

Although the same configuration user interfaces (D-series product versions of PUP
and COUP and G-series product versions of SCF) are used for magnetic, optical,
and virtual disk processes, there are variances in the individual commands
between the different disk types.

Storage pool administration may require new operational procedures. For example,
when operators add new physical disks to a system, they may need to add them to
storage pools as well. Conversely, when they delete disks, operators may need to
remove all references to logical files on them and also remove the disks from the
storage pool.

Operational and application procedures for storage administration may also require
some modification. Note that SMF generally manages storage at a storage pool
level, automatically distributing logical files across all volumes in the storage pool.
This method can defeat existing applications and operational procedures that
perform similar functions. For example, operational procedures set for running The
Process KMSF Conventional
$ZSMS 3.3 MB 2.0 MB
Pool process 2.5 MB 2.0 MB
Virtual disk process 5.0 MB Zero