Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP 9000 Networking: Advanced Server/9000 Administrator's Guide > Chapter 6 Logging and Tuning

Tuning

» 

Technical documentation

Complete book in PDF
» Feedback
Content starts here

 » Table of Contents

 » Index

AS/U server performance is sensitive to client usage levels. To improve performance from clients to AS/U servers, connections are established with the TCP No Delay option. This option removes a delay for certain SMB transactions.The registry values and lanman.ini parameters are set to default levels that should be appropriate for the average installation. Tuning individual parameters for specific server usage can often improve performance. Two such parameters that are sensitive to tuning are the registry value VCDistribution and the lanman.ini parameter maxclients.

The default value for the registry value LockNapInMSec is based on benchmark tuning. The optimal value for a particular installation is workload-dependent and may require some experimentation to determine.

Configuring NetBIOS Memory Usage

The configurable kernel parameter nrfc_nb allows you to specify the maximum number of NetBIOS connections that will be in use on a system. This parameter is used to tune the amount of memory used by NetBIOS.

Acceptable Values:

Minimum: 100

Maximum: 2048

Default: 1024

The number of connections is closely bound to the system memory usage. More memory will be used when more connections are configured. Too little memory will prevent NetBIOS from operating properly. Therefore, unless it is needed, we do not recommend changing the default value. Increase the value if you receive either of the following NetBIOS warning messages on the console or syslog: the rfcnb warning message "Resource map low" or "No resource map available."

The value can be modified through SAM or by editing the /stand/system file on the system. An error will be returned if the value is outside the boundaries of the minimum and maximum values.

Batch Oplocks Performance

Batch oplocks, used by Windows NT, are implemented in this release. Unlike exclusive oplocks, which allowed a client to open a file for exclusive access, batch oplocks enable a client to repeatedly open and close a file without forcing a remote server to physically open and close it. A client can keep a file open until another client wants to modify it (for example, to move the file, delete the file, get file information, or set file information). This process more efficiently handles DOS, which traditionally forces batch files to be opened and closed each time a line is read.

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1997 Hewlett-Packard Development Company, L.P.