Performance Tuning for Content Manager

270 Performance Tuning for Content Manager

How to view or set

1. In the administrative console, select the application server you are tuning.

2. Under Additional Properties, click Web Container Service.

3. Under Additional Properties, click Thread Pool.

4. Select the check box Growable thread pool.

5. Click Apply to ensure that the changes are saved.

6. Stop and restart the application server.

Our recommendation

This option is intended to handle brief loads beyond the configured maximum

thread size. However, use caution when selecting this option because too many

threads can cause the system to overload.

9.5.4 Max keep-alive connections (MaxKeepAliveConnections)

This parameter describes the maximum number of concurrent connections to the

Web container that are allowed to be kept alive (that is, to be processed in

multiple requests. The Web server plug-in keeps connections open to the

application server as long as it can. However, if the value of this property is too

small, performance is negatively affected because the plug-in has to open a new

connection for each request instead of sending multiple requests through one

connection. The application server might not accept a new connection under a

heavy load if there are too many sockets in TIME_WAIT state.

If all client requests are going through the Web server plug-in and there are many

TIME_WAIT state sockets for port 9080, the application server is closing

connections prematurely, which decreases performance. The application server

will close the connection from the plug-in, or from any client, for any of the

following reasons:

 The client request was an HTTP 1.0 request when the Web server plug-in

always sends HTTP 1.1 requests.

 The maximum number of concurrent keep-alives was reached. A keep-alive

must be obtained only once for the life of a connection (that is, after the first

request is completed, but before the second request can be read).

 The maximum number of requests for a connection was reached, preventing

denial of service attacks in which a client tries to hold on to a keep-alive

connection forever.

 A timeout occurred while waiting to read the next request or to read the

remainder of the current request.

Default values

No default setting