02 Things you need to know
Server
HP-UX settings
Note: These settings require modifications to SAM to allow some of the parameters to be given values greater than those normally allowed by SAM.
It is strongly recommended that you use the HP-UX system administration utility sam to configure your Notes server machine as an OLTP/Database Server machine and then modify settings. To do this:
1. Bring up sam.
2. Select and open Kernel Configuration.
3. Select and run Configurable Parameters.
4. Choose Actions->Apply Tuned Parameter Set...
5. Select "General OLTP/Database Server System" and click "OK".
6. Select each of the parameters in the following table and:
a. Choose "Actions->Modify Configurable Parameter..."
b. Be sure the "Specify New Formula/Value" button is selected
c. Enter the "Value" from the table into the "Formula/Value:" text box
d. Click "OK"
Parameter | Value |
| NSTREVENT | 50 |
| NSTRPUSH | 16 |
| NSTRSCHED | 0 |
| STRMSGSZ | 65535 |
| aio_max_ops | (nkthread) |
| max_thread_proc | (nkthread*8)/10 |
| maxdsiz | 0x20000000 |
| maxfiles | 4096 |
| maxfiles_lim | 4096 |
| maxtsiz | 0x0C000000 |
| ncallout | (nkthread) |
| nflocks | (nfile/2) |
| nkthread | ((nproc*8)+16) |
| shmseg | 64 |
7. Select Process New Kernel from the Actions menu.(This rebuilds your kernel resources to handle the requirements of a Notes server).
Heavy client loads, or Notes applications that consume a great deal of kernel resources, may require that parameters be set even higher than the recommended values shown above. Some guidelines for setting particular parameters are listed below. Note that HP supplies a real time monitoring tool called Glance Plus. Glance Plus is on the HP Applications CD and is useful for monitoring the status of these values while the application is running. If other applications are also being used concurrently on the system, please use caution when modifying these values.
maxfiles and maxfiles_lim: This is the soft (and hard) limit on the number of file descriptors per process. Large numbers of active clients and/or large number of open files may require that this value be increased. (Note that even the recommended value is greater than the maximum value SAM allows by default, and SAM's configuration settings must be modified to allow greater values for these to parameters. The release note 'HP-UX - Modify maxfiles and maxfiles lim' covers this configuration issue).
nkthread: This is the total number of threads system-wide. As a general rule Lotus recommends that this number be three times the number of concurrent clients the system is intended to host, at minimum.
nfile: This is the total number of files that can be opened system-wide. As a general rule Lotus recommends that this number be (5 times the number of active domino users + 2048) for the system.
nflocks: This is the total number of file locks for open files system-wide. As a general rule Lotus recommends that this number be greater than 1/2 the value of nfile (explained above).
nproc: This is the total number of processes system-wide. Domino uses threads. The nproc does not have a direct relationship to the number of clients and it should not normally be necessary to increase its value. Note that other parameters are calculated based on nproc, and increasing its value may result in those other parameters going out of their allowed range.
ninode: This is the total number of inodes system-wide. If there is a large number of unique open files, this parameter may need to be increased.
maxdsize: This affects the amount of dynamic memory available. Heavy client loads may require increasing this value.
Some additional factors you should keep in mind include:
- Increasing the values of some kernel parameters affect the amount of memory used by the kernel. On small memory systems (those close to the min recommend) you might generate a kernel that will not boot, or there might not be enough resources left to run the desktop environment.
- Certain parameters have maximum values which SAM checks for. Also, since some parameter are calculated from other parameters, increasing one parameter may cause another to go out of range.
- Some parameter are constrained to be related to others in certain ways (such as max_thread_proc <= nkthread).
Topics