Microsoft recommends that the Windows NT PAGEFILE.SYS file(s) be set to physical RAM + 12 MB for the initial size and physical RAM + half of physical RAM for the maximum size. Microsoft recommends that the Windows 2000 PAGEFILE.SYS file(s) be set to 1.5 times the amount of physical RAM.
If you used additional SQL services such as Full-Text Search service, the size of PAGEFILE.SYS file(s) should be increased.
To increase the size of PAGEFILE.SYS file(s), you can do the following:
1. Double-click the Control Panel System applet and select the Performance tab.
2. Click the "Virtual Memory" button.
3. Set appropriate size of the PAGEFILE.SYS file(s).
4. Restart the computer.
Spreading paging files across multiple disk drives and controllers improves performance on most disk systems because multiple disks can process input/output requests concurrently.
Run regedit and choose:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Set DisablePagingExecutive to 1 and reboot the server box.
This can increase SQL Server performance, because Windows NT will allocate more RAM to SQL Server than to its file cache.
To set this option, you can do the following:
1. Double-click the Network icon in Control Panel.
2. Click the Services tab.
3. Click Server to select it, and then click the Properties button.
4. Click Maximize Throughput for Network Applications, and then click OK.
5. Restart the computer.
Run regedit and choose:
HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisableLastAccessUpdate
Add key NtfsDisableLastAccessUpdate as REG_DWORD and set it to "1".
Because each protocol uses RAM and CPU, you can remove unused protocols to release resources for SQL Server using.
Try to remove from startup IIS service, FTP server service, Gopher, SMTP, WINS, DHCP, Directory Replicator and so on, if you do not need to use these services. You can start these services manually when you will need them.
If you installed several protocols, Windows NT negotiates network connections in the order that the protocols are prioritized in the network services binding list. So, the first protocol in the binding list will be used before the other installed protocols. You can improve the overall performance by setting the most frequently used protocol to the first place in the binding list.
Because each Performance Monitor counter uses some server resources, it is a great idea to use as few counters in Performance Monitor, as possible.
Because Open GL screen savers use a lot of system resources, it is a great idea to not use them on a server box.
Because each type of Audit Policy events uses some server resources, it is a great idea to use as few types of Audit Policy events, as possible. Try to not use "File and Objects Access" and "Process Tracking" Audit Policy events, because they most resource expensive in comparison with other Audit Policy events.
This ensures that background applications (SQL Server, for example) will get higher priority than foreground applications.
To set the performance boost for the foreground applications to "None", you can do the following:
1. Double-click the Control Panel System applet and select the Performance tab.
2. On the Application Performance box drag the arrow to set the boost to "None".
Run regedit and choose:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management
Set IoPageLockLimit to the maximum bytes you can lock for I/O operations.
See this link for more details: How can I improve I/O performance?
No comments:
Post a Comment