Sun Microsystems Netscape Enterprise Server, Administrator'S Manual

Page: 225 / 532

Chapter 10, Configuring the Server for Performance 225
Miscellaneous magnus.conf Directives
Miscellaneous magnus.conf Directives
You can use the following
magnus.conf
directives to configure your server to
function more effectively:
•
RqThrottle
(See “About RqThrottle” on page 229)
•
PostThredsEarly
(See “PostThreadsEarly” on page 243)
•
MaxProcs
(See “Multi-process Mode” on page 225)
•
MinAcceptThreadPerSocket
and
MaxAcceptThreadPerSocket
(See“Accept Thread Information” on page 227)
•
MinCGIStubs
,
MaxCGIStubs
, and
CGIStubIdleTimeout
(See
“CGIStub Processes (Unix)” on page 227)
•
SndBufSize
and
RcvBufSize
(See “Buffer Size” on page 228)
•
NativePoolStackSize
/
NativePoolQueueSize
/
NativePoolMaxThreads
/
NativePoolMinThreads
(See “Native
Thread Pool Size” on page 229)
Multi-process Mode
The Enterprise Server can be configured to handle requests using multiple
processes and multiple threads in each process. This flexibility provides optimal
performance for sites using threads and also provides backward compatibility
to sites running legacy applications that are not ready to run in a threaded
environment. Because applications on Windows NT generally already take
advantage of multi-process considerations, this feature mostly applies to Unix
platforms.
The advantage of multiple processes is that legacy applications which are not
thread-aware or thread safe can now be run more effectively in Enterprise
Server 4.0. However, because all the Netscape extensions are built to support a
single-process, threaded environment, they cannot run in the multi-process
mode. WAI, LiveWire, Java, Server-side JavaScript, LiveConnect and the Web
Publishing and Search plugins fail on startup if the server is in multi-process
mode. There are two approaches to multi-thread design:
• Enterprise Server with a single process
• Enterprise Server with multiple processes