Server

The Windows NT Server service’s responsibility is to establish sessions with remote stations and receive SMB (Server Message Block) request messages from those stations. (SMB requests are typically used to request the Server service perform I/O-such as open, read, or write on a device or file located on the Windows NT Server station).

· You can configure the Windows NT Server service’s resource allocation (and associated nonpaged memory pool usage) by using the Control Panel Network application. When you use the Control Panel Network application to configure the Windows NT Server service software, you are presented with the following Server Optimization Level dialog:

You may want to consider a specific setting, depending on factors such as how many users will be accessing the system and the amount of memory in the system. The amount of memory allocated to the Windows NT Server service (for such resources as InitWorkItems, MaxWorkItems, RawWorkItems, MaxPagedMemory, MaxNonPagedMem, ThreadCountAdd, BlockingThreads, MinFreeConnections, and MaxFreeConnection) differs dramatically based on your choice.

· The "Minimize Memory Used" level is meant to accommodate up to 10 remote users simultaneously using Windows NT Server.

· The "Balance" option is for up to 64 remote users.

· The "Maximize Throughput for File Sharing" is for 64 or more remote users. With this option set, file cache access has priority over user application access to memory (the value of LargeSystemCache in the registry changes to 0x1). Use this option if you are using Windows NT Server for file server capabilities. This is the default setting!

SYSTEM\CurrentControlSet\Control\

Session Manager\Memory Management\

LargeSystemCache

· The "Maximize Throughput for Network Applications" is for 64 or more remote users. However, with this option set, users’ application access has priority over file cache access to memory (the value of LargeSystemCache in the registry changes to 0x0).

This is not valuable to MS-SQL Server because this BackOffice product does it’s own memory management. This is only valuable to Client/Server applications that do not do their own memory management.

 

So you be the judge !!!!!