The webserver should be set up to allow browsers to cache content, as specified in the “Instructing web browsers to cache content” section of the Info Center:
Also apply the rules detailed in the “Determining which files to compress” section of the Info Center (http://publib.boulder.ibm.com/infocenter/ltscnnct/v2r0/topic/com.ibm.connections.25.help/t_ihs_config_not_compressing_files.html
Comment out the AddOutputFilterByType DEFLATE directives from step 4 if compression is being done by a reverse proxy. The other rules should be enabled so proper VARY headers are applied.
The key tuning parameter for IBM HTTP Server is to ensure that the total number of threads the http server can accept is at least as large as the total number of WebContainer threads defined in WebSphere.
For Windows, only the ThreadsPerChild and ThreadLimit settings needs to be changed. These values should be equal.
For other operating systems, a hybrid approach is used with multiple "servers", each running multiple threads. In this case, MaxClients should be set to the WebContainer total instead of ThreadsPerChild. TheadsPerChild & ServerLimit should be set so that their values, multipled together, are equal to MaxClients. Also consider setting MaxSpareThreads to a value close to MaxClients so that spikes in load can be handled without allocating new processes or threads.
Users can enable mod_status to monitor the number of threads in use.