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

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

Chapter 10, Configuring the Server for Performance 237
Using perfdump Statistics to Tune Your Server
connection and is now waiting for a new request to arrive on the same
connection. If the server has more than the maximum waiting connections
open when a new connection starts to wait for a keepalive request, the server
closes the oldest connection. This algorithm keeps an upper bound on the
number of open, waiting keepalive connections that the server can maintain.
Enterprise Server does not always honor a KeepAlive request from a client. The
following conditions cause the server to close a connection even if the client
has requested a KeepAlive connection:
•
KeepAliveTimeout
is set to 0.
•
MaxKeepAlive
count is exceeded.
• Dynamic content, such as CGI, does not have an HTTP
content_length
header set or the header is not lowercase.
• Request is not
HTTP GET
or
HEAD
.
• HTTP 1.1 pipelined request.
• The request was determined to be bad-- if have bad client sends only
headers, no content.
When SSL is enabled,
KeepAliveTimeout
defaults to 0, which effectively
disables persistent connections. If you want to use persistent connections with
SSL, set
KeepAliveTimeout
to a non-zero value.
You can also change
KeepAliveTimeout
in the Performance Tuning page in
the Server Manager.
AcceptTimeout
The number of seconds the server will wait for data from the client after
accepting the connection before sending the request to the unaccelerated path.
Tuning
If
AcceptTimout
is set to a small number, rather than reading the initial read
from clients with slow responses, the read may timeout and have to be read on
the second attempt. This may impact performance.