OSI/MHS Configuration and Management Manual

Sizing and Tuning Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
8-10
OSI/MHS Capacity Limitations
Disk and Disk Cache
The disk storage requirement for OSI/MHS varies from several hundred megabytes for
a very small configuration to many thousands of megabytes for a very large
configuration. Your HP analyst can help you determine the amount of disk space
required. (As much as 30% of the disk space required is for TMF audit trails.)
It is critical to define the amount of disk cache to take advantage of the memory
available in your system. A suitable setting will depend on available memory, the size
of the disk volume, and the number of files. You can use the Peripheral Utility Program
(PUP) to determine whether the current amount of disk cache is sufficient: if the
percentage of cache hits is not in the high 90s, consider dedicating more memory to
the cache.
Processors
The number of processors required to run OSI/MHS varies widely according to
message traffic, processor type, and other types of applications that coexist in the
system. A configuration requiring six K1000 processors might require only two K10000
processors. (Most configurations of OSI/MHS are larger than this example.)
OSI/MHS Capacity Limitations
Table 8-1 describes the OSI/MHS subsystem capacity limitations.
Table 8-1. OSI/MHS Subsystem Capacity Limitations (page 1 of 2)
Subsystem Component Capacity
Number of adjacent MTAs 800
Number of routes unlimited
Number of alternate routes per MTA 7
Number of processes in the subsystem 400
Number of MS APPLs per MS process 1000
Number of MR groups 133; limited only by the
maximum of 400 per subsystem
Number of gateways 16: only one P1 exit, only one
Transfer gateway
Number of APPLs per gateway unlimited
Message size for delivery to a GPI gateway 10 MB
Message size for delivery to a Transfer gateway 2 MB
Message size for delivery to, or submission by, a local
user agent
10 MB
Message size for delivery to, or submission by, a remote
user agent
2 MB
Message size for relay to an adjacent MTA 10 MB