![[Contents]](FIGURE/CONTENT.GIF)
Nonstop Database, HiRDB Version 9 System Operation Guide
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
Normally, startup processing of resident processes is executed during HiRDB startup processing. As the number of resident processes increases, the HiRDB startup processing time also increases. As a guideline, it takes approximately one second to start one process in a server machine with a performance rating of about 100 MIPS.
When the system switching facility is used, it might be desirable to consider reducing the HiRDB startup processing time.
The number of resident processes is determined by the value of the first parameter in the pd_process_count operand.
The second parameter in the pd_process_count operand is specified. The following describes the processing depending on whether the second parameter is specified.
All resident processes are started during HiRDB startup processing. In this case, HiRDB cannot start unless all the resident processes (500 processes in this example) start successfully. If a server machine with a performance rating of approximately 100 MIPS is used in this example, it takes some 500 seconds to start all the resident processes during HiRDB startup processing.
Some resident processes are started during HiRDB startup processing, and the rest are started after HiRDB startup processing is completed. In this case, HiRDB starts if some of the resident processes (50 processes in this example) start successfully. If a 100-MIPS server machine is used in this example, it takes some 50 seconds to start the resident processes during HiRDB startup processing. The remaining resident processes (450 processes in this example) are started after HiRDB startup processing is completed.
Assume that the following system is used:
When this facility is used, check and, if necessary, revise the PDCWAITTIME operand's value in the client environment definition.
All Rights Reserved. Copyright (C) 2011, 2015, Hitachi, Ltd.