|
Performance Registry
Secrets Table of contents |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Services for Macintosh Services for Macintosh (SFM) lets Macintosh-based computers transparently access Windows NT network shares. You can tune the performance of these connections with registry entries. You should consider adjusting these values if you have a LAN that depends on the responsiveness of Windows NT share access from Macs. VI-24 The following entries’ values control the amount of paged and nonpaged memory that SFM uses as it processes operations. Under heavy workloads, SFM memory requirements rise, and if it can allocate all the memory it requires in one request, its performance improves. However, raising these values can cause other applications, including Windows NT itself, to be unable to allocate memory when they need to.
The value in the first key above sets the paged memory limit; the default is 20,000 K. The second key sets the limit of nonpaged memory; the default is 4,000 K. Dynamic Host Configuration Protocol VI-26 Dynamic Host Configuration Protocol (DHCP) dynamically assigns IP addresses from a pool of allowable addresses to other machines on a LAN. This registry entry determines whether the DHCP server logs all IP address assignments to a database file. You can then use this database to track down problems in network configuration or behavior. However, logging each DHCP invocation can significantly reduce system performance. If your DHCP seems to be highly stable, you might consider turning off this flag to improve performance.
The default value of 1 enables DHCP logging; change the value to 0 to disable this feature. NetBEUI NetBEUI is a transport that has been migrated forward from LanManager and Windows for Workgroups 3.11. The NetBEUI transport is named NBF in Windows NT. VI-27 This value controls the time NBF waits before resending Logical Link Control (LLC) messages if they are not acknowledged. You should change this registry entry to raise this value if NBF is running over a slow network.
The value specifies, in 100-nanosecond increments, the timeout period for unacknowledged LLC messages. The default is 600 milliseconds. VI-28 This entry controls the number of LLC frames NBF sends before it stops sending and waits for acknowledgment. On a very reliable system, you can increase this number and improve performance. If your network is less reliable, raising the value is not wise because the performance benefit of raising the value is offset by retry operations.
The value sets the number of frames NBF sends before waiting for acknowledgment. The default value is 1. VI-29 This entry determines the number of times NBF retries a request when it gets a T1 timeout. If your NBF is running on a slow network, you might want to increase this value.
A value of 1 or more sets the number of times NBF retries a request; a value of 0 sets no limit on the number of NBF’s retries. The default value is 8. NetLogon The NetLogon service manages the process of logging on to a domain. It interacts with the NT Local Security Authority (LSA) to validate account and password information. It also keeps all account information synchronized between the Primary Domain Controller (PDC) and the Backup Domain Controllers (BDCs). VI-30 NetLogon collects account information for a specified period of time and sends it in one batch to each BDC that isn’t already up-to-date. By default, NetLogon determines the interval based on the server’s load, but you can tune the time period NetLogon collects account data to suit your environment or to minimize network traffic.
The value is the number of seconds in the collection period. The default value is 300 seconds, or 5 minutes. Valid values range from 60 to 172,800 (48 hours). VI-31 When a BDC receives a pulse from the PDC, it waits a specified time before returning a message. Changing this entry changes the wait period.
The value is the number of seconds that a BDC waits before requesting updated information from a PDC after receiving a pulse. The default value is 1; valid values range from 0 to 120. Typically, you should keep this value small, less than the PulseTimeout1 value under the same key. VI-32 The following entry specifies how many outstanding pulses the PDC has at any time. By adjusting this value you can control the load on a PDC — the higher the value, the higher the potential load when security or account information is updated. Decreasing the value increases the time required to propagate the information to all the BDCs. You can estimate the time it takes to replicate account or security database information with the formula ((Randomize/2) * NumberOfBdcsInDomain) / PulseConcurrency
The value is the number of outstanding pulse events the PDC allows. The default value is 20; valid values range from 0 to 500. TCP/IP VI-33 TCP/IP allows a certain number of bytes to be sent before the system waits for an acknowledgment. You can increase this number, also known as the Window Size, if your network is reliable and has high bandwidth. Ideally, it should be a multiple of the TCP Maximum Segment Size (MSS).
The value is the size, in bytes, of the TCP/IP window. The default is 8760 in Ethernet networks; valid values range from 0 to 0xFFFF. NWLink NWLink is an implementation of the IPX/SPX protocols popular in NetWare networks. The NWNBLink module provides support for the Novell implementation of the NetBIOS protocol. VI-34 By default, the NWNBLink protocol allocates two frames to receive messages. When the frames are filled, it sends an acknowledgment to the sender. This entry is typically used as a clocking mechanism where the sender is on a fast part of the LAN but the receiver is on a slow link. You can set the value to 0 to prevent NWNBLink from sending any acknowledgments, which can improve performance. Note that you can direct NWNBLink to ignore the AckWindow if round-trip times are below a threshold indicated in the AckWindowThreshold value under the same key.
The value determines the number of frames in the AckWindow that are filled with received messages before NWNBLink sends an acknowledgment. If the value is 0, not acknowledgments are sent. The default value is 2. VI-36 While NWNBLink sessions are initialized, the maximum number of messages that the receiver can process at one time is transmitted to the sender. Increasing this value may increase performance on high-bandwidth networks.
The value sets the number of frames allocated for receiving message. The default value is 4. Valid values range from 0 to 49152. VI-37 This entry determines how many messages can be received simultaneously; the value is sent to remote connections. Increasing this value could increase performance of IPX messaging on high-bandwidth networks.
The value is the number of frames allocated for receiving SPX messages. The default value is 4; valid values range from 1 to 10. VI-38 This value specifies how many messages can be received simultaneously; it is sent to remote connections. Increasing this value could increase performance of SPX messaging on high-bandwidth networks.
The value is the number of frames allocated for receiving SPX messages. The default value is 4. Valid values range from 1 to 11. FILE SYSTEM PERFORMANCE VI-39 This entry is the only performance-altering value related to file systems that you can control in the registry. By default, NTFS creates an MS-DOS-style “short file name” for every file created with a long file name; otherwise, these files won’t be recognized by Windows 3.1 and MS-DOS programs running on NT. NTFS must therefore track two names for these files, which can cause performance to degrade, particularly the performance of directory-related operations such as file look-ups.
The value determines whether short names are generated for long file names. A value of 0 means that NTFS generates short names; a value of 1 means that NTFS doesn’t generate the short names. If you don’t run any Windows 3.1 or MS-DOS programs on your system, you don’t need short file name compatibility; disable this value. PRINTING PERFORMANCE VI-40 The print spooler thread is responsible for feeding data to printers. By default, it runs in the NORMAL_PRIORITY_CLASS, along with most of the other threads in a system. However, you can reduce this value, which may enhance the responsiveness of other more important applications such as the file system server (LanmanServer).
The value sets the class the print spooler thread runs in. The following three values are recognized; other values are ignored.
REGISTRY EDITOR PERFORMANCE VI-41 Normally, when RegEdit processes a .reg file, it bring up a dialog box informing you that it added items to the registry. Using this feature is usually a good option, unless you want to add certain items automatically with a login script and you don’t want users to have to click OK to close the window every time they log on. Luckily, Microsoft has provided an undocumented parameter for RegEdit that bypasses this option: the /y parameter. Use it like this: Regedit /y <regfile.reg>Note that this change only affects Regedit.exe, not Regedt32.exe or Regedt.exe. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Page: 1, 2 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||