Performance Tuning for Content Manager

262 Performance Tuning for Content Manager

How to view or set

This parameter, <RefreshInterval=xxxx> (where xxxx is the number of seconds),

is specified in the websphere_root/config/plug-in.xml file.

Our recommendation

Use the default. Content Manager is not directly affected by this parameter.

9.4.3 HTTP server maximum clients (MaxClients)

The MaxClients directive controls the maximum number of simultaneous

connections or users that the Web server can service at any one time. If, at peak

usage, your Web server needs to support 200 active users at once, you should

set MaxClients to 220 (200 plus an extra 10% for load growth). Setting

MaxClients too low can cause some users to believe that the Web server is not

responding. You should have sufficient RAM in your Web server machines to

support each connected client. For IBM HTTP Server 1.3 on UNIX, you should

allocate about 1.5 MB MaxClients of RAM for use by the IBM HTTP Server. For

IBM HTTP Server 1.3 on Windows, you should allocate about 300 KB MaxClients

of RAM for use by the IBM HTTP Server. Some third-party modules can

significantly increase the amount of RAM used per connected client.

Default values

150

How to view or set

1. Edit the IBM HTTP server file httpd.conf, which is located in the directory IBM

HTTP Server_root_directory/conf.

2. Change the value of the MaxClients parameter.

3. Save the changes and restart the IBM HTTP server.

Our recommendation

Initially use the default and monitor your system performance. In general:

 Use a lower MaxClients value for a simple, CPU-intensive application.

 Use a higher MaxClients value for a more complex, database-intensive

application with longer wait times.

9.4.4 Minimum spare server processes (MinSpareServers)

The MinSpareServers directive sets the desired minimum number of idle child

server processes. An idle process is one that is not handling a request. If the