TITLE:              NWL Server Optimization and Functions
DOCUMENT ID:        TID1200430
DOCUMENT REVISION:  2
DATE:               11Apr95
ALERT STATUS:       Yellow
README FOR:         NA

NOVELL PRODUCT and VERSION:
NETWARE LITE V1.1

ABSTRACT:
NA

---------------------------------------------------------------------
DISCLAIMER: THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR
EXTERNAL TO NOVELL.  NOVELL MAKES EVERY EFFORT WITHIN ITS MEAN TO
VERIFY THIS INFORMATION. HOWEVER, THE INFORMATION PROVIDED IN THIS
DOCUMENT IS FOR YOUR INFORMATION ONLY. NOVELL MAKES NO EXPLICIT OR
IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
---------------------------------------------------------------------

ISSUE:

NetWare Lite Server Optimization and Functions

Disk Caches

NetWare Lite does not ship with a disk cache.  Novell has tested with
several (read many) commercially available disk cache products and
found them to be quite inexpensive while adding significant
performance to the NetWare Lite server software.  For higher
performance of the NetWare Lite server, Novell suggests that you
acquire a disk cache and install it on the server machines.  Some
cache tuning may be necessary for best results.

Server Configuration

For best performance, Novell suggests that you increase receive
buffer and read buffer sizes to what is supported by the network
topology (such as Ethernet, Token-Ring) up to a maximum of 4096 bytes
using a multiple of 512 bytes.  In fact, if 4096 is selected then the
server will truncate the value to the maximum value supported by the
topology.  This tuning allows clients to request more data from (or
send more data to) the server with each read (write) operation.  When
more data is sent, fewer requests are necessary and better
performance is obtained.  This enhancement does increase the size of
server when it is resident in DOS. 

Depending on the load being placed on the server, it may be
beneficial to increase the number of receive buffers and read
buffers.  In general, Novell found that 8 to 12 receive buffers are
enough for even the most heavily loaded server.  Similarly, 5 to 10
read buffers are sufficient. These values do not need to be more than
one or two above the number of  simultaneous connections (up to the
suggested maximums of 8 to 12 receive buffers and 5 to 10 read
buffers).

MAP verses DOS' SUBST command

If your machine is a server and you would like to map to the server,
it is recommended that you SUBST to the server instead of mapping to
server.  SUBST is a DOS command that lets you assign a drive letter
to a directory on another drive.

Example:

If you usually map to the server with the G: drive to the Network
Directory APPS and APPS is actually the C:\APPS directory, the NET 
MAP G: APPS command could be replaced by SUBST G: C:\APPS command. To
remove this substitution, you would type SUBST G: /D. 

Using this substitution rather than a mapping will result in better
performance for operations done on the G: drive.

Mapping Local Drive

You can map drives that are local (A: or B:) and use them temporarily
as network drives.  However, as a general practice, it is not
recommended.   If you run out of drive letters to map, increase
LASTDRIVE in your CONFIG.SYS.

Use of ASSIGN

Do not use ASSIGN with NetWare Lite.  The DOS reference manual (3.3)
recommends that you use SUBST instead of ASSIGN and explains how to
do so.

---------------------------------------------------------------------
Any trademarks referenced in this document are the property of their
respective owners. Consult your product manuals for complete
trademark information.
---------------------------------------------------------------------