Sun Microsystems Netscape Enterprise Server, Руководство администратора

Страница: 236 / 532

Using perfdump Statistics to Tune Your Server
236 Netscape Enterprise Server Administrator’s Guide
This setting is not tunable.
Thread limits <min/max>
The minimum thread limit is a goal for how many threads the server attempts to
keep in the WaitingThreads state. This number is just a goal. The number of
actual threads in this state may go slightly above or below this value.
The maximum threads represents a hard limit for the maximum number of
active threads that can run simultaneously, which can become a bottleneck for
performance. Enterprise Server 3.6, has default limits of 48/512. For more
information, see “About RqThrottle” on page 229.
Tuning
See “About RqThrottle” on page 229.
KeepAlive Information
KeepAliveInfo:
------------------
KeepAliveCount 0/200
KeepAliveHits 0
KeepAliveFlushes 0
KeepAliveTimeout 30 seconds
This section reports statistics about the server’s HTTP-level KeepAlive system.
Note
The name “KeepAlive” should not be confused with TCP “KeepAlives.” Also,
note that the name “KeepAlive” was changed to “Persistent Connections” in
HTTP/1.1, but for clarity this document continues to refer to them as
“KeepAlive” connections.
Both HTTP/1.0 and HTTP/1.1 support the ability to send multiple requests
across a single HTTP session. A web server can receive hundreds of new HTTP
requests per second. If every request was allowed to keep the connection open
indefinitely, the server could become overloaded with connections. On Unix
systems, this could lead to a file table overflow very easily.
To deal with this problem, the server maintains a “Maximum number of
‘waiting’ keepalive connections” counter. A ‘waiting’ keepalive connection is a
connection that has fully completed processing of the previous request over the