Sun Microsystems Netscape Enterprise Server, Administrator'S Manual

Page: 256 / 532

Common Performance Problems
256 Netscape Enterprise Server Administrator’s Guide
Common Performance Problems
This section discusses a few common performance problems to check for on
your web site:
• Low-Memory Situations
• Under-Throttled Server
• Cache Not Utilized
• KeepAlive Connections Flushed
• Log File Modes
• Using Local Variables
Low-Memory Situations
If you need Enterprise Server to run in low-memory situations, try reducing the
thread limit to a bare minimum by lowering the value of
RqThrottle
in your
magnus.conf
file. Also you may want to reduce the maximum number of
processes that the Enterprise Server will spawn by lowering the value of the
MaxProcs
value in the
magnus.conf
file.
Under-Throttled Server
The server does not allow the number of active threads to exceed the Thread
Limit value. If the number of simultaneous requests reaches that limit, the
server stops servicing new connections until the old connections are freed up.
This can lead to increased response time.
In Enterprise Server, the server’s default
RqThrottle
value is 512. If you want
your server to accept more connections, you need to increase the
RqThrottle
value.
Checking
The symptom of an under-throttled server is a server with a long response time.
Making a request from a browser establishes a connection fairly quickly to the
server, but on under-throttled servers it may take a long time before the
response comes back to the client.