User Guide

34 Server Memory Administration Guide
Server Memory Administration Guide
103-000147-001
August 30, 2001
Novell Confidential
Manual 99a38 July 17, 2001
access the server console to run MONITOR and execute any console
commands.
In most cases, NetWare Remote Manager is more useful than MONITOR
when diagnosing server memory problems. For more information, see the
NetWare Remote Manager Administration Guide.
The MONITOR utility provides statistics that indicate how efficiently
memory is being used by the server and individual modules. For more
information, see MONITOR in Utilities Reference.
Settable parameters and console commands let you tune the memory
system to achieve optimal performance. For more information, see SET
> Memory Parameters in Utilities Reference.
Using Protected Address Spaces
You can use a portion of server memory called a protected address space to
protect the server operating system from untried or troublesome applications
and to use virtual memory. When applications are loaded into a protected
address space, they can't corrupt the operating system, cause server abends, or
corrupt other applications that are running in other protected address spaces.
All protected address spaces use virtual memory, so running modules in a
protected address space also uses RAM more efficiently.
For general information about protected address spaces and the applications
that can be loaded into them, see “Protected Address Spaces” on page 12. For
general information about virtual memory, see “Virtual Memory” on page 14.
Because modules loaded into a protected address space have controlled
interaction with the operating system, all modules that must communicate
with each other by directly importing another module’s data or functions
(such as those of an e-mail application or a database) should be loaded
into the same protected address space.
If you load a NetWare Loadable Module
TM
(NLM
TM
) that depends upon
another module, such as CLIB, the other module will be loaded
automatically into the same address space.
If the same module is loaded into more than one address space, the
module's code will be shared among the address spaces. Therefore,
loading the module into multiple address spaces does not require
additional memory for the module itself. Only data for the required
module is unique for each address space.