Tuning client-request processing

Edit online

For large installation environments, NIM can be scaled to support anywhere from 20 to 150 client requests simultaneously. NIM scaling is done by enabling the multithreaded option on the nimesis daemon.

The multithreaded option provides better handling of the volume of client information change requests and client state changes. Without the use of the multithreaded option, the NIM master can become overloaded by activity on the NIM database and the number of active processes, resulting in simultaneous failures during the installation of a large number of client machines.

The multithreaded nimesis daemon will serialize and buffer NIM client requests to protect the NIM master from process overload, without causing significant performance degradation. The user must understand that many of the client information changes will not be reflected in the NIM database. The most recent information changes for any client, however, are eventually processed. Debugging of failed or hung clients will not be adversely affected.

The number of threads assigned to this daemon determines how many simultaneous NIM client requests can be handled in the NIM environment. Because most of the NIM client requests are processed rapidly, it is not necessary to have one thread for every client installing. The number of threads needed to support the activities in a NIM environment is dependent upon several items. The following should be considered when determining the number of threads:

  • Number of clients that will be operated on at the same time
  • Processing capacity of the NIM master machine
  • What type of operations are planned

In general, one thread can support two to four clients that are installing BOS at the same time. For example, when installing 150 machines, 50 to 75 threads is sufficient. The number of threads is highly dependent on the processing power of the NIM master machine, and slower master machines may require more threads.

For smaller NIM environments, enabling the multithreaded daemon can monopolize system resources on the master that will not be used. For example, when installing 50 machines simultaneously, 20 to 25 threads or even the single-threaded daemon would suffice.

Note: The multithreaded option alone will not allow more machines to be installed simultaneously. The multithreaded option should be used in conjunction with global export of NIM resources, distribution of NIM resources throughout the NIM environment, and a network environment capable of handling a large volume of throughput.